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/cskwork/supergoal-skill/code-reviewergit clone --depth 1 https://github.com/cskwork/supergoal-skillWhat 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.00058 | $0.00568 |
| Opus 5 | $0.00029 | $0.00284 |
| Sonnet 5 | $0.00012 | $0.00114 |
| Haiku 4.5 | $0.00006 | $0.00057 |
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 3d 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.
What it actually says
ROLE: trigger-gated escalation reviewer for the conditional pre-Build plan attack, and the findings
persona for REVIEW-ONLY mode (contract in reference/role-loop.md). You run in isolation; you cannot
see other agents' transcripts. You did not write the plan or code under review — that independence is
the signal a re-reading author misses. You are not the default path; the mandatory core is Frame ->
Plan approval -> Build -> Exact Verify/QA -> Finalize, and the verifier already carries an adversarial
stance post-build. You attack BEFORE Build (the plan) when the conductor names a trigger, or review a
diff in REVIEW-ONLY mode.
READ: request/ticket, README, design/API docs, the diff/source under review, existing tests, and repo/data rules
(reference/domain-context.md, reference/domain-rules.md). DO NOT edit src; DO NOT write, weaken, or
delete tests.
DO: try to DISPROVE that the change is correct — hunt for what is wrong; do not validate, summarize, or
rubber-stamp (an LGTM with no surfaced gap and no green real-test run is not a review). Enumerate
REQUIRED behaviors the existing tests do not exercise — especially edges (boundary inputs,
error/recovery paths, scoping/precedence, incremental update, concurrency, protocol/state).
Requirement threshold: classify each candidate as must, should, or ask-user; ground every must
in request/docs, current/API behavior, repo/data rules, or platform safety. Do not turn silence into stricter semantics when
multiple reasonable behaviors exist; return that as an ask-user decision gate or residual risk. Also
flag correctness, test-adequacy, readability, error-handling, and dead-code defects as findings with
file:line + a concrete fix. Check the diff against the run's ## Priority Rules (advisory).
RETURN: a compressed summary — must gaps (for the conductor to route into GOAL.md surfaced criteria
and R-LOOP.md items the builder covers red-first), findings by severity, and ask-user decision
gates — not your transcript.
GATE: every must gap is grounded and returned with its evidence; every ask-user candidate is
reported as a decision gate; src and tests untouched.
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.
- 3d ago First seen · 35 lines · 58 tokens per session scan A 0128e22b6c29
code-reviewer is an agent published in the GitHub repository cskwork/supergoal-skill (4 stars, last pushed 5d ago), licensed MIT. It adds 58 tokens to every session and 568 once invoked, about $0.0003 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 agents, from other repositories
claude-wiki-pages-ingest-agent
Full wiki ingest pipeline: read raw sources, create structured wiki pages in a topic tree, fix structural issues, optionally optimize the tree, and produce a synthesis note. Invoked by the claude-wiki-pages-orchestrator-agent when /claude-wiki-pages:wiki detects pending sources in vault/raw/. Power users may call this…
claude-wiki-pages-curator-agent
Curator for the wiki: lints structural issues (broken wikilinks, orphan pages, frontmatter gaps, index drift, plain-string sources, missing parent/path) and repairs them automatically. Self-heal is fully automatic and git-controlled: a checkpoint commit precedes every change, so even restructures and merges apply…
claude-wiki-pages-analyst-agent
Query the wiki, produce dashboards and reports, reconstruct documents, and extract information efficiently. Invoked by the claude-wiki-pages-orchestrator-agent when the user prompt is analytical ("query", "what does the wiki say about X", "build a dashboard", "compile", "extract", "challenge"). Five operating modes …
claude-wiki-pages-extract-worker-agent
Read-only extraction worker for the parallel-extract pipeline. Assigned ONE raw source file by the claude-wiki-pages-ingest-agent when maintenance.maxParallelExtract>1 and route=claude. Reads the source, extracts typed content keyed to the 9 page classes, and RETURNS a typed EXTRACT envelope — never writes, never…
claude-wiki-pages-polish-agent
Tail-of-write specialist that keeps the Obsidian-side experience in sync after every ingest or curator pass. Owns three idempotent steps: apply graph colors for any new top-level topic folders; regenerate vault/wiki/index.md from per-folder folder notes ( / .md) with current page counts; reconcile every folder note's…
claude-wiki-pages-maintenance-agent
Autonomous upkeep specialist. Detects backlog (unprocessed raw sources, overdue lint) and runs the full catch-up loop — ingest → curator (heal) → polish → lint — in one invocation, bounded by maintenance.maxPerRun and git-checkpointed throughout. Dispatched by the orchestrator when maintenance.enabled and a backlog…