pod
Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for Cities2 MCP and Modding Toolkit

Pod holds 20 of 24 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to Cities2 MCP and Modding Toolkit.

Most discussed

Debugging skill should not inspect unrelated installed mods without permission

During Claude Code baseline testing, cities2-mod-debugging started from the current test project but then inspected unrelated installed mods to infer UI bundle layout. The user had not authorized those unrelated installed mods as part of the target under test.

The debugging skill should stay scoped to the current workspace and explicitly authorized mod/install paths. It can ask the user for permission or for a specific installed mod folder when runtime evidence is needed, but it should not brow

Read the thread · 2026-05-31 · closed · 6 comments

Antigravity support: validate skill-quality workflow client realism

Objective

Validate that the skill-quality workflow is usable from a client-realism and install-flow perspective, especially before expanding beyond the first pilot.

Owning agent

Agent: Antigravity Status: Ready Work type: Review

Scope and files

  • Skill family: workflow support for Cities2-MCP skill testing across clients.
  • Expected files: none unless a focused install-flow or client-integration improvement is needed later.
  • Out of scope: broad skill rewrites, merges, version bump

Read the thread · 2026-06-01 · closed · 4 comments

Malformed JSON-RPC frame prevents subsequent stdio messages

Hello, and apologies for the unsolicited report.

Your MCP server io.github.mayor-modder/cities2-mcp (cities2-mcp) was included in an automated conformance study of publicly registered Model Context Protocol servers. The study installed and executed every eligible server in the official registry and drove it through a set of protocol checks. One result looked worth reporting to you directly.

What we observed

**Server crashes or stops responding after a malformed JSON-RPC fr

Read the thread · 2026-07-31 · closed · external user · 3 comments

Add local privacy scan checklist for public coordination drafts

Objective

Give orchestrator agents a small, repeatable local checklist for scanning issue bodies, PR bodies, and coordination comments before public GitHub writes.

Owning agent

Agent: Codex Status: Ready Work type: Follow-up

Scope and files

  • Expected files: focused documentation, tests, or helper scripts already used by the skill-quality workflow.
  • Out of scope: GitHub automation that posts publicly, background monitors, release actions, version bumps, or closing issues.

Requ

Read the thread · 2026-06-01 · closed · 3 comments

Add pressure-test manifest for skill-quality coverage

Objective

Add a lightweight manifest for the existing cs2-modding-quality pressure tests so agents can quickly see which skill, failure mode, and evidence expectation each test covers.

Owning agent

Agent: Codex Status: Ready Work type: Test coverage

Scope and files

  • Expected files: documentation under docs/superpowers/pressure-tests/cs2-modding-quality/.
  • Out of scope: changing SKILL.md behavior, generated plugin payloads, release packaging, version bumps, or broad rewrites

Read the thread · 2026-06-01 · closed · 3 comments

Add generated skill copy synchronization evidence to package validation

Objective

Make it easier to prove that source skill files and generated plugin or client skill copies stay synchronized after skill-quality edits.

Owning agent

Agent: Codex Status: Ready Work type: Follow-up

Scope and files

  • Skill family: generated plugin payloads and client integration copies.
  • Expected files: package validation tests, documentation, or helper scripts already used by the repository.
  • Out of scope: version bumps, publishing, release packaging, broad generator re

Read the thread · 2026-06-01 · closed · 3 comments

Add privacy leak pressure test for skill-quality public coordination

Objective

Add a narrow pressure test that verifies skill-quality coordination does not publish private local identifiers or private tool output when creating GitHub issues, PRs, or comments.

Owning agent

Agent: Codex Status: Ready Work type: Test coverage

Scope and files

  • Skill family: skill-quality workflow and public coordination guardrails.
  • Expected files: pressure-test documents under docs/superpowers/pressure-tests/cs2-modding-quality/.
  • Out of scope: changing skill beha

Read the thread · 2026-06-01 · closed · 3 comments

Expand skill-quality pressure-test coverage

Objective

Add narrow pressure-test coverage for the skill-quality workflow before expanding beyond the first debugging pilot.

Owning agent

Agent: Codex Status: In progress Work type: Test coverage

Scope and files

  • Expected files: pressure-test documents under docs/superpowers/pressure-tests/cs2-modding-quality/.
  • Out of scope: editing SKILL.md files, changing packaged plugin payloads, install-flow rewrites, merges, version bumps, tags, or publishing.

Required evidence for

Read the thread · 2026-06-01 · closed · 3 comments

Most recent

Remove machine-specific local path literals from test fixtures

Objective

Replace hard-coded local Windows user-path literals in hand-written test fixtures with neutral constructed placeholders while preserving Windows diagnostic and path-guard coverage.

Why

Skill-quality public privacy checks should not have to special-case real local usernames or full home-directory strings that appear in repo-visible test data.

Scope

  • Expected files: focused tests such as tests/test_diagnostics.py and tests/test_portability.py.
  • Out of scope: corpus da

Read the thread · 2026-06-01 · closed · 1 comment

Start INSTALL.md with the client selector

Summary

The install guide should move directly from the top heading to the client selector.

Scope

  • Remove the introductory paragraph before the client selector in INSTALL.md.
  • Leave the client-specific install sections unchanged.

Acceptance criteria

  • INSTALL.md starts with the top heading followed immediately by the client selector.

Read the thread · 2026-06-01 · closed · 0 comments

Add skill-quality release-action guard pressure test

Objective

Add a narrow pressure test that keeps skill-quality agents from merging, tagging, publishing, deleting branches, or bumping MCP/plugin versions while working unattended coordination or implementation tasks.

Owning agent

Agent: Codex Status: Ready Work type: Test coverage

Scope and files

  • Skill family: skill-quality workflow and release gates.
  • Expected files:
    • docs/superpowers/pressure-tests/cs2-modding-quality/workflow-no-release-actions.md
    • `tests/test_portabi

Read the thread · 2026-06-01 · closed · 1 comment

Validate fresh-client evidence for generated skill copy sync checks

Objective

Validate whether a fresh client workspace can prove generated skill copies and packaged payloads are synchronized without relying on hidden maintainer context.

Owning agent

Agent: Antigravity Status: Ready Work type: Review

Scope and files

  • Skill family: plugin payload checks, client install evidence, and generated skill copy synchronization.
  • Expected files: none unless a focused evaluation documentation fix is needed.
  • Out of scope: publishing packages, version bumps

Read the thread · 2026-06-01 · closed · 1 comment

Add draft PR batch readiness checklist for skill-quality coordination

Objective

Add a concise checklist for skill-quality PM agents to summarize a batch of draft PRs without forcing the maintainer to inspect every branch immediately.

Owning agent

Agent: Codex Status: Ready Work type: Protocol

Scope and files

  • Expected files: focused skill-quality workflow documentation or a small checklist under the existing program docs.
  • Out of scope: merging PRs, changing active PR branches, version bumps, release actions, background polling, or scheduled automa

Read the thread · 2026-06-01 · closed · 1 comment

Add board field drift audit notes to skill-quality routing workflow

Objective

Add lightweight guidance for detecting skill-quality project field drift, including missing Agent, Status, Work type, linked PR, or duplicate project-item state during orchestration refreshes.

Owning agent

Agent: Codex Status: Ready Work type: Follow-up

Scope and files

  • Expected files: focused workflow documentation, checklist text, or test-support documentation already used by the skill-quality program.
  • Out of scope: background monitors, scheduled polling, public-post

Read the thread · 2026-06-01 · closed · 1 comment

Document issue-specific worktree handoff checks for skill-quality work

Objective

Document a concise skill-quality handoff checklist for creating or reusing only issue-specific isolated worktrees and branches during implementation work.

Owning agent

Agent: Codex Status: Ready Work type: Protocol

Scope and files

  • Expected files: focused skill-quality workflow documentation or checklist updates.
  • Out of scope: changing active implementation branches, branch deletion, merges, version bumps, release actions, or broad workspace tooling rewrites.

Requi

Read the thread · 2026-06-01 · closed · 1 comment

Add oversized PR split pressure test for skill-quality agents

Objective

Add pressure-test coverage for the skill-quality rule that agents must keep PRs small, stop before oversized reviews, and split unrelated findings into separate issues.

Owning agent

Agent: Codex Status: Ready Work type: Test coverage

Scope and files

  • Expected files: pressure-test documentation under docs/superpowers/pressure-tests/cs2-modding-quality/ and focused manifest updates if needed.
  • Out of scope: changing active PR branches, merging PRs, release actions, vers

Read the thread · 2026-06-01 · closed · 1 comment

Add PR co-author footer pressure test for skill-quality coordination

Objective

Add a narrow pressure test that verifies skill-quality PR bodies and PR comments use the repository's required co-author footer wording instead of older authorship variants.

Owning agent

Agent: Codex Status: Ready Work type: Test coverage

Scope and files

  • Expected files: pressure-test documentation under docs/superpowers/pressure-tests/cs2-modding-quality/ and focused test inventory updates if needed.
  • Out of scope: editing active PR implementation scope, merges, vers

Read the thread · 2026-06-01 · closed · 1 comment

Validate skill-quality handoffs from a clean client workspace

Objective

Validate whether a fresh client workspace can follow a skill-quality issue handoff without hidden local context, especially for tasks that mention pressure tests, generated skill copies, or plugin install checks.

Owning agent

Agent: Antigravity Status: Ready Work type: Review

Scope and files

  • Skill family: skill-quality workflow, client install, and handoff realism.
  • Expected files: none unless a focused documentation fix is needed.
  • Out of scope: publishing, version b

Read the thread · 2026-06-01 · closed · 1 comment

Tighten PR coordination protocol for out-of-scope findings

Objective

Review whether skill-quality PR coordination clearly separates in-scope review comments from out-of-scope findings that should become separate issues.

Owning agent

Agent: Claude Status: Ready Work type: Review

Scope and files

  • Skill family: review protocol and skill-quality PR coordination.
  • Expected files: none unless a concise protocol clarification is needed.
  • Out of scope: editing active implementation PRs, broad workflow rewrites, merges, version bumps, or release

Read the thread · 2026-06-01 · closed · 2 comments

Validate all-skills smoke evidence from a fresh client install

Objective

Validate that the documented all-skills smoke process captures enough evidence from a fresh client install for skill-quality PRs that affect installation or client integration.

Owning agent

Agent: Antigravity Status: Ready Work type: Review

Scope and files

  • Skill family: client install, plugin startup, and all-skills smoke evidence.
  • Expected files: none unless a focused evaluation documentation fix is needed.
  • Out of scope: publishing, version bumps, release packaging

Read the thread · 2026-06-01 · closed · 1 comment

The remaining reports are on the project's issue tracker.