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/adtn0810/truestackWrote 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/adtn0810/truestack/truestack-verify)<a href="https://agentmods.dev/commands/adtn0810/truestack/truestack-verify"><img src="https://agentmods.dev/badge/commands/adtn0810/truestack/truestack-verify/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/adtn0810/truestack/truestack-verify"><img src="https://agentmods.dev/badge/commands/adtn0810/truestack/truestack-verify.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.00042 | $0.00145 |
| Opus 5 | $0.00021 | $0.00072 |
| Sonnet 5 | $0.00008 | $0.00029 |
| Haiku 4.5 | $0.00004 | $0.00015 |
Grade A, and why
truestack-verify 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 9d 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
Use the truestack-quality-control skill to run a complete quality sweep.
Scope: $ARGUMENTS If no scope is given, check all current uncommitted changes. Read the intent (plan / acceptance criteria) and project memory first, run every layer, and end with the QC verdict (DONE / NOT DONE / NEEDS EVIDENCE) and the evidence behind it. Report only what you actually ran.
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.
- 9d ago First seen · 11 lines · 42 tokens per session scan A 85eaaac1fdc5
truestack-verify is a command published in the GitHub repository adtn0810/truestack (2 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 145 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 commands, from other repositories
full-review
Orchestrate comprehensive multi-dimensional code review using specialized review agents across architecture, security, performance, testing, and best practices.
double-check
Comprehensive verification with automated quality gates, confession gathering, and confidence-based issue filtering. Default: self-review with gates. --deep: multi-agent review via code-reviewer agent. Use before committing, after fixing bugs, or to validate feature completeness.
review-skills
Review changed skills: automated bash checks + 9 structural dimensions (D1-D9) + 5 intent checks (M1-M5). PASS/FAIL verdict. Fix in-place.
codex-loop
Use Codex as a second, differently-trained reviewer of your branch, fix every real finding with regression tests, and loop until two consecutive reviews come back clean. Runs autonomously.
p5-impl-refactor
Improves code quality without changing behavior. All tests must continue to pass.
p5-review-code
Checks code for quality, clean code, logic errors and test coverage. Delivers review findings with severity level.