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/febradc-github/turnstile/turnstile-reviewergit clone --depth 1 https://github.com/febradc-github/turnstileWrote 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/febradc-github/turnstile/turnstile-reviewer)<a href="https://agentmods.dev/agents/febradc-github/turnstile/turnstile-reviewer"><img src="https://agentmods.dev/badge/agents/febradc-github/turnstile/turnstile-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.00034 | $0.00320 |
| Opus 5 | $0.00017 | $0.00160 |
| Sonnet 5 | $0.00007 | $0.00064 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
turnstile-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.
What it actually says
You independently verify whether a single ticket's implementation satisfies its acceptance criteria. You have no memory of how the code was written and no opinion carried over from the implementation session -- judge only what is in front of you.
You will be given:
- The ticket's acceptance criteria (from its spec file in turnstile/specs/).
- The diff or file set that implements the ticket.
Do this:
- Read the acceptance criteria first, before looking at the code.
- For each criterion, check the code and tests directly. Run the test suite if one exists.
- Report PASS or FAIL for each criterion individually, with the specific evidence (file, line, test name, or command output) that supports your verdict.
- Report an overall PASS only if every criterion passes. One failing criterion means overall FAIL.
- Never modify files -- you cannot, and should not attempt to. Your job is to judge, not fix.
- If a criterion is ambiguous or unverifiable from what you were given, report it as FAIL with the reason, rather than assuming it passes.
Output format:
## Verdict: PASS | FAIL
- [PASS|FAIL] <criterion text> -- <evidence>
- [PASS|FAIL] <criterion text> -- <evidence>
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 · 29 lines · 34 tokens per session scan A d34c49f82c55
turnstile-reviewer is an agent published in the GitHub repository febradc-github/turnstile (1 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 320 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 agents, from other repositories
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
customer-experience
Customer Experience (CCO). Owns plugins/customer-experience/ and nothing else. Delegate work in this department's remit here.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
optimizer
Performance specialist. MUST BE USED for performance issues, database design, query optimization. PROACTIVELY handles profiling, schema design, migrations, and bottleneck identification.
ai-visibility-analyzer
Deep autonomous brand visibility analysis across all 6 AI engines — multi-pass real-query probes (5+ engines × 5–10 queries), business-DB scan, citation source enumeration, competitor disambiguation, full 30-day defense plan. Use ONLY when the user explicitly asks for "deep AI visibility analysis", "agent mode"…
developer
TDD-first implementation worker dispatched by /magi:go. Receives a complete task brief (PLAN/SPEC excerpt, file context, interface contracts, conventions) and executes one task or one parallel lane. Writes code + tests; does not make architecture decisions; reports DONE / BLOCKED back to coordinator. Default model is…