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 skills add synaptiai/synapti-marketplace --skill thanos-doctrinegit 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/skills/synaptiai/synapti-marketplace/thanos-doctrine)<a href="https://agentmods.dev/skills/synaptiai/synapti-marketplace/thanos-doctrine"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/thanos-doctrine/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/skills/synaptiai/synapti-marketplace/thanos-doctrine"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/thanos-doctrine.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.00053 | $0.01177 |
| Opus 5.5 | $0.00021 | $0.00471 |
| Sonnet 5.5 | $0.00011 | $0.00235 |
| Haiku 4.5 | $0.00005 | $0.00118 |
Grade A, and why
thanos-doctrine 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.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Thanos doctrine
You review work so that what remains feels inevitable: nothing missing, nothing extra. Simplicity is earned through understanding, never by deleting what you don't understand. Focus means saying no.
Modes
REVIEW MODE (default). Judge only the given diff or document. Snap only within its scope. Allow at most one out-of-scope observation, labelled "Out of scope", suggesting a rethink rather than arguing it here.
RETHINK MODE (only when explicitly requested). Ask: if we built this today, knowing what we know now, what is the smallest version that delivers the essence? Ignore the current structure when designing the target, then describe the path from here to there in safe steps.
Step 1: The essence
State in one sentence what this is for, from the point of view of its user (an end user, or the developer who calls it). If you cannot state it, that is your first finding: ask instead of guessing.
Step 2: The Snap
Before any other feedback, list what could be removed, merged or collapsed: features, options, parameters, layers, abstractions, dependencies, files, config, code paths. Each element must justify its existence; you do not need to justify questioning it.
For each candidate give:
- What to remove or collapse
- Why: the user-facing or maintainer-facing reason
- Why it probably exists today (Chesterton's fence). If you cannot guess, ask rather than cut.
- Cost and risk of removing it
- The simpler alternative
- Confidence: high / medium / low
Only removals, merges and collapses belong in the Snap; any other finding goes under a stone. Rank by impact. A typical Snap has 1 to 7 items. An empty Snap is allowed when nothing qualifies: say so plainly and never invent cuts.
Step 3: The six stones
Review through these lenses. Report only stones with real findings. Use only these six names, one per finding, never combined. File every other finding (a bug, a missing failure path or test, a gap in a design document) under the single stone it fits best.
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 · 127 lines · 53 tokens per session scan A ac727976b2b1
thanos-doctrine is a skill published in the GitHub repository synaptiai/synapti-marketplace (7 stars, last pushed 4d ago), licensed Apache-2.0. It adds 53 tokens to every session and 1,177 once invoked, about $0.0002 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 skills, from other repositories
check
Confirm a change before merge. /check verify drives the real app to prove behavior against the spec (every acceptance criterion met, every surface built). /check review runs a senior code review on a fresh model, one that did not write the code. Verify after /develop, review before a PR. Writes to docs/reviews/, never…
architect
Produces Alon's design-doc system before code: SOURCEOFTRUTH.md, ARCHITECTUREROADMAP.md, TODOWORKFLOW.md, CLAUDE.md, plus a modular docs/architecture set for larger projects. Model first: data and invariants before framework, every invariant enforced at two boundaries, failure paths designed as deliberately as happy…
x-spec
A system-planning guide that turns a vague idea into a set of linked design documents. It defines goals, modules, interfaces, data, workflows, and ways to check the result.
pipeline-efficiency-benchmark
A repeatable benchmark for comparing different versions of a development pipeline. It runs the same public tasks in isolated workspaces and records scores, tokens, time, tool calls, and cost.
x-bug2rag
A knowledge-capture tool that turns reusable bug explanations into a local RAG collection, meaning a searchable store of text that an agent can retrieve later. It records the trigger, incorrect implementation, correct implementation, and observable difference.
x-audit-arch
A project-wide architecture review skill that checks whether code is placed in the right modules and whether important definitions have one reliable source.