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/adtn0810/truestack/truestack-loopgit 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-loop)<a href="https://agentmods.dev/commands/adtn0810/truestack/truestack-loop"><img src="https://agentmods.dev/badge/commands/adtn0810/truestack/truestack-loop.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.1 | $0.00033 | $0.00198 |
| Opus 5 | $0.00016 | $0.00099 |
| Sonnet 5 | $0.00007 | $0.00040 |
| Haiku 4.5 | $0.00003 | $0.00020 |
Grade A, and why
truestack-loop 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 6d 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
Drive the work to a proven-done state, don't stop at "it compiles".
Target: $ARGUMENTS
Use the build loop (truestack-backend-development) for a feature or the verify-or-loop (truestack-root-cause-debugging) for a bug: implement/fix → run truestack-quality-control → if a criterion or the repro still fails, identify exactly what and why, fix, and re-run. Loop until all acceptance criteria pass and (for a bug) the original reproduction no longer triggers. If genuinely blocked, stop and report an honest score (criteria met / total + what blocks each unmet one) rather than looping forever or claiming done.
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.
- 6d ago First seen · 14 lines · 33 tokens per session scan A 188265d3538c
truestack-loop is a command published in the GitHub repository adtn0810/truestack (2 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 198 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
verify
Run verification loop to validate implementation.
verify-loop
자동 재검증 루프 (최대 3회 재시도, 실패 시 자동 수정).
ui-smoke.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
ui-snapshot.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
backprop
Trace a bug back to a spec gap and generate regression tests.
p6-exploratory
Conducts unstructured, experience-based tests that automated tests and defined test cases do not cover. The goal is to find unexpected behaviours, usability issues, and hidden bugs that remain invisible in structured testing.