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 commands/reviewtoolkits/cpython-review-toolkit/exploregit clone --depth 1 https://github.com/ReviewToolkits/cpython-review-toolkitWhat 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.00012 | $0.02183 |
| Opus 5 | $0.00006 | $0.01092 |
| Sonnet 5 | $0.00002 | $0.00437 |
| Haiku 4.5 | $0.00001 | $0.00218 |
Grade A, and why
explore 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 2d 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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comprehensive CPython C Code Exploration
Run a comprehensive analysis of CPython C source code using multiple specialized agents, each focusing on a different aspect of C code quality. The include-graph-mapper runs first to provide structural context for all subsequent agents.
Arguments: "$ARGUMENTS"
Argument Parsing
Parse arguments into three categories:
Scope (path or glob):
.or omitted → entire project (default)Objects/→ specific directory treeObjects/listobject.c→ specific fileModules/_io/→ specific module
Aspects (which agents to run):
includes→ include-graph-mapper onlyrefcounts→ refcount-auditorerrors→ error-path-analyzergil→ gil-discipline-checkercomplexity→ c-complexity-analyzerstyle→ pep7-style-checkernull-safety→ null-safety-scannerdeprecation→ api-deprecation-trackermacros→ macro-hygiene-reviewermemory→ memory-pattern-analyzerrecursion→ recursion-guard-auditorpyerr-clear→ pyerr-clear-auditoruninit-dealloc→ uninitialized-dealloc-auditorft-races→ ft-race-scannerstw-safety→ stw-safety-checkerlock-discipline→ lock-discipline-checkerinit-bypass→ init-bypass-checkerparity→ parity-checkerhistory→ git-history-analyzerall→ all agents (default)
Note: recursion, pyerr-clear, uninit-dealloc, ft-races, stw-safety, and
lock-discipline, and init-bypass are the tree-sitter-based detectors (require
pip install tree-sitter tree-sitter-c). The tsan-report-analyzer,
tsan-stress-generator, and oom-reproducer agents are on-demand dynamic
tools (they need a built interpreter — a --disable-gil+TSan build, or a build
providing _testcapi.set_nomemory), not part of the static explore pipeline; see
the reproduce command.
Options:
deep→ full detail, no output truncationsummary→ summary tier only (faster)parallel→ run agents concurrently where possible--max-parallel N→ cap concurrent agents per group (default: 2)
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.
- 2d ago First seen · 246 lines · 12 tokens per session scan A a60077641fe3
explore is a command published in the GitHub repository ReviewToolkits/cpython-review-toolkit (10 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 2,183 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.