Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add mayor-modder/Cities2-MCP --skill cities2-mod-reviewgit clone --depth 1 https://github.com/mayor-modder/Cities2-MCPWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/mayor-modder/cities2-mcp/cities2-mod-review)<a href="https://agentmods.dev/skills/mayor-modder/cities2-mcp/cities2-mod-review"><img src="https://agentmods.dev/badge/skills/mayor-modder/cities2-mcp/cities2-mod-review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mayor-modder/cities2-mcp/cities2-mod-review"><img src="https://agentmods.dev/badge/skills/mayor-modder/cities2-mcp/cities2-mod-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00035 | $0.01652 |
| Opus 5 | $0.00017 | $0.00826 |
| Sonnet 5 | $0.00007 | $0.00330 |
| Haiku 4.5 | $0.00003 | $0.00165 |
Grade A, and why
cities2-mod-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cities2 Mod Review
Review the mod as a good-faith quality pass: find practical risks, missing evidence, and user-impacting gaps. Prefer documented best practices from the MCP server when judging CS2-specific APIs, packaging, UI, localization, saves, and toolchain behavior.
Review Sources
- Inspect the mod files, build/package config, README/release notes, logs, screenshots, and test notes when available.
- Use MCP server wiki/reference lookup for CS2 modding claims before treating them as a best practice.
- Separate normative modding constraints from descriptive gameplay statements. Gameplay facts explain what the game does; modding constraints say what the mod should or must do safely.
- Separate evidence levels in findings: observed in project files, supported by MCP or project documentation, and inferred recommendation. Do not present an inference as a sourced rule.
- Do not infer React, a loader pattern, runtime requirement, or packaging requirement from a filename alone. A
.tsxfile only proves TypeScript JSX syntax; require package dependencies, imports, templates, or documentation before naming React or prescribing React-specific fixes. - If a CSS file is not imported, bundled, or otherwise loaded by inspected files, describe its current impact as no effect. Keep any global-theme or runtime styling risk conditional on evidence that the CSS becomes loaded.
- If source access is partial, say what was reviewed and what remains unknown.
- For diff, branch, or PR-style reviews, identify the reviewed range or changed files, compare against the user request or plan, inspect affected call sites, and state if no diff or requirements were available.
- When judging readiness, name the exact evidence that would prove the next stage: clean build, package artifact, installed package/playset smoke launch, local playtest results or notes, relevant logs, and UI debugger or screenshots for UI mods. Keep local playtest separate from install/playset launch; do not collapse it into "installed local package/playset launch" or "smoke-test in a local playset." If the scaffold cannot build yet, still list local playtest results or notes as a downstream gate after the build/package blockers are fixed.
- If readiness is absent, unproven, or blocked, end with a
Readiness evidence still needed:line or list that explicitly names: clean build, package artifact, installed package/playset smoke launch, local playtest results or notes, logs, and UI debugger or screenshots for UI mods.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 106 lines · 35 tokens per session scan A b5264c9649ac
cities2-mod-review is a skill published in the GitHub repository mayor-modder/Cities2-MCP (9 stars, last pushed 17d ago), licensed MIT. It adds 35 tokens to every session and 1,652 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
lifeblood-mcp
Use when an agent should work with Lifeblood's MCP semantic-code tools: analyzing C# or Unity workspaces, querying symbols/dependencies/blast radius/file impact/test impact, checking architectural invariants, validating edits with compilecheck/diagnose, or choosing the right Lifeblood tool instead of grep-style…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
okx-cex-portfolio
This skill should be used when the user asks about 'account balance', 'how much USDT do I have', 'my funding account', 'show my positions', 'open positions', 'position P&L', 'unrealized PnL', 'closed positions', 'position history', 'realized PnL', 'account bills', 'transaction history', 'trading fees', 'fee tier'…
isuzu-unity-cli
Control Unity Editor from the CLI with the isuzu-unity-cli command. Execute C# code, browse scene hierarchy, inspect/modify GameObjects, capture screenshots, read console logs, check compile status, control play mode, and execute menu items. Use when: user wants to interact with Unity Editor programmatically, run C#…
godot-code-review
Use when reviewing GDScript or C# Godot code — checklist of best practices, common anti-patterns, and Godot-specific pitfalls.
code-review
Review ServiceNow server-side scripts for ES5 violations, ACL/injection/XSS issues, N+1 queries, missing setLimit/error handling, hard-coded sysids, and business-rule recursion risks.