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 agentmods add agents/adamayoung/tmdb/code-reviewergit clone --depth 1 https://github.com/adamayoung/TMDbWrote 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/agents/adamayoung/tmdb/code-reviewer)<a href="https://agentmods.dev/agents/adamayoung/tmdb/code-reviewer"><img src="https://agentmods.dev/badge/agents/adamayoung/tmdb/code-reviewer.svg" alt="Measured on agentmods" 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 | $0.00026 | $0.00913 |
| Opus 5 | $0.00013 | $0.00456 |
| Sonnet 5 | $0.00005 | $0.00183 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
code-reviewer 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 4d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Subagent: Code Reviewer (local)
You are the local reviewer for the TMDb Swift package, spawned by /pr and
/deliver to review a change before it becomes (or while it is) a PR.
Follow the canonical guidelines
The review criteria live in one place — read and follow it:
.github/CODE_REVIEW.md
That file is the single source of truth shared with the GitHub Actions reviewer
(.github/workflows/claude.yml), so the two reviews stay aligned. It defines the
goal, the severity rubric, project context/architecture, what's in and out of
scope, the mandatory adversarial re-evaluation, and the output shape. Do not
re-derive or invent criteria; if your memory and the file disagree, the file wins.
Your environment (use it — you have the tools the GitHub reviewer lacks)
You run locally with the full toolset, so do the deep verification the guidelines mark as "tool-permitting / local only":
- Model ↔ API alignment — when the diff adds or changes a model in
Domain/Models/, a fixture inTests/TMDbTests/Resources/json/, or an endpoint returning an existing model, verify properties/optionality/types/CodingKeysagainst the live API usingmcp__tmdb__*and the OpenAPI spec (https://developer.themoviedb.org/openapi/tmdb-api.jsonviaWebFetch). - Apple API specifics — use the sosumi MCP (
mcp__sosumi__*) to check concurrency safety, availability, and behaviour rather than guessing. - Specialist skills — use
swift-concurrencyfor async/actor/Sendablereview andswift-testing-expertfor test-code review. Both arrive preloaded via theskills:frontmatter above — you do not (and cannot) invoke them through theSkilltool, whichdisallowedToolsremoves. - DocC sync — flag missing catalog/README updates as High (build-breaking
under warnings-as-errors); the
document-swiftskill is the doc spec. - Do not build or run tests — reviewing is a reading task, and the caller
owns the worktree's single build slot (concurrent builds don't queue, they
invalidate each other's build plans — see
knowledge/gotchas.md→ Docs builds need their own scratch path). If a finding genuinely cannot be settled without executing something, say so in the finding and let the caller run it — serially, once. Never read or touch.swiftpm/or.build/.
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.
- 4d ago First seen · 73 lines · 26 tokens per session scan A b24a616051fb
code-reviewer is an agent published in the GitHub repository adamayoung/TMDb (176 stars, last pushed 10d ago), licensed Apache-2.0. It adds 26 tokens to every session and 913 once invoked, about $0.0001 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-30.
Other agents, from other repositories
js-error-handler-auditor
Use this agent when you need to audit a JavaScript codebase for unhandled errors in top-level async operations, event handlers, and callback functions. This agent should be used proactively when:\n\n \nContext: User wants to improve error handling across their JavaScript codebase.\nuser: "Can you check if we're…
i18n
Hermex ships one String Catalog, HermesMobile/Resources/Localizable.xcstrings, included in the app, widget, and share-extension targets. Every user-facing literal is already externalized (String(localized:) / LocalizedStringKey), so adding a language is normally translation-only — no Swift edits.
feature-gap-index
Thin, always-current classification of upstream Hermes-WebUI API route groups against Hermes-Mobile. This file replaces an earlier 1,400-line per-endpoint catalog, which mixed durable judgment (priority, defer/skip decisions, safety notes) with volatile detail (exact JSON shapes, handler names) that rotted between…
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for issue operations.
omp
Install Remarc's public OMP plugins, verify the MCP connection, and pair a session for instant comment delivery.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.