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.
git clone --depth 1 https://github.com/synaptiai/synapti-marketplaceWrote 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/commands/synaptiai/synapti-marketplace/rethink)<a href="https://agentmods.dev/commands/synaptiai/synapti-marketplace/rethink"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/rethink/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/synaptiai/synapti-marketplace/rethink"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/rethink.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00032 | $0.00307 |
| Opus 5.5 | $0.00013 | $0.00123 |
| Sonnet 5.5 | $0.00006 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
rethink 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
/rethink
Rethink mode. The subsystem to rethink is the text Claude Code appends
after ARGUMENTS: at the end of this command; with no such line, it is
empty.
Steps
-
If the subsystem is empty, ask the user which subsystem to rethink (a path or a short description) and stop. Do not invoke the subagent.
-
Otherwise invoke the
thanossubagent with the Agent tool and this prompt:RETHINK MODE. Target: <the subsystem, verbatim> Locate it in the repository (it may be a path or a description), read it and its callers, then answer with the thanos-doctrine method: the smallest version that delivers the essence, designed without regard to the current structure, and a stepwise, safe path from the current state to that target. Return it in the doctrine's output format. -
Show the subagent's review to the user exactly as returned: no preface, summary, or commentary before or after it.
Do not edit files, apply suggestions, or start any of the steps the review proposes.
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 · 35 lines · 32 tokens per session scan A d49a8b4bc411
rethink is a command published in the GitHub repository synaptiai/synapti-marketplace (7 stars, last pushed 4d ago), licensed Apache-2.0. It adds 32 tokens to every session and 307 once invoked, about $0.0001 per session on Opus 5.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-10-16.
Other commands, from other repositories
create-worktree
Follow these steps to create a git worktree.
production-upgrade
Run the full product upgrade pipeline — 55-agent iterative review with CEO/Engineering/UX/QA parallel loops.
review
Pre-landing code review — analyzes diff for SQL safety, LLM trust boundaries, conditional side effects, missing tests, dependency risks, and security issues.
review
Run code-review and security-review skills against the current diff. Safe to run repeatedly during Build.
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.