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/rigos0/superturtle/code-reviewgit clone --depth 1 https://github.com/Rigos0/superturtleWhat 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.00000 | $0.00336 |
| Opus 5 | $0.00000 | $0.00168 |
| Sonnet 5 | $0.00000 | $0.00067 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
code-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 yesterday.
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
Run a code review. User input: $ARGUMENTS
What this does
Launches two review agents in parallel: code-reviewer (bugs, security, correctness) and arch-reviewer (structure, duplication, bloat). No browser, no UX — code only.
Step 1: Determine scope
- If
$ARGUMENTSis empty → review unstaged changes. If no unstaged changes, review the last commit (HEAD~1..HEAD). - If
$ARGUMENTScontains a scope (e.g., "staged changes", "commits since main", a commit range) → use that scope.
Step 2: Check scope size
Run git diff --stat (or git diff <range> --stat) to count files in scope.
- ≤10 files → launch one
code-reviewer+ onearch-reviewer, both with full scope, in parallel. - >10 files → split changed files into chunks of ~5-7 files. Launch one
code-reviewerper chunk + onearch-reviewerfor the full scope, all in parallel.
The arch-reviewer always gets the full scope — it needs the big picture.
Step 3: Present results
Merge all reports into one. Deduplicate findings across agents. Order by severity (critical first).
## Code Review
**Scope:** {range} ({N files}, +X -Y)
**Verdict:** CLEAN | ISSUES FOUND
### Critical
...
### Warning
...
### Nit
...
### Architecture
...
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.
- yesterday First seen · 43 lines · 0 tokens per session scan A 98282e9fc3af
code-review is a command published in the GitHub repository Rigos0/superturtle (123 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 336 tokens. 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 commands, from other repositories
open-code-review
Invoke the professional code review Agent CLI tool OpenCodeReview (OCR) to review current code changes, and let the Agent autonomously decide whether to apply fixes.
delegate-review
Run OCR in delegation mode — OCR handles file selection and rules, the host agent performs the actual review.
commit
Please summarize your current changes, generate a commit message in English, then add and commit.
global-shortcuts
Global shortcuts do not use the renderer command registry. Electron main registers them with globalShortcut.register, so they can run while the app is unfocused.
speckit.archive
Archive a feature specification into main project memory after merge, resolving gaps and conflicts.
speckit.extract.run
Extract knowledge, guidelines, and ADRs from one or more completed spec directories into the project documentation system.