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/avansaber/tailtest/summarygit clone --depth 1 https://github.com/avansaber/tailtestWhat 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.00000 | $0.00101 |
| Opus 5 | $0.00000 | $0.00051 |
| Sonnet 5 | $0.00000 | $0.00020 |
| Haiku 4.5 | $0.00000 | $0.00010 |
Grade A, and why
summary 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 2d 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
Show a summary of this tailtest session.
Read .tailtest/session.json. If the file does not exist or generated_tests is empty, say:
"No tests were generated this session."
Otherwise output a plain-text summary following the tailtest /summary format in CLAUDE.md.
Also write the summary to the report_path stored in session.json (create .tailtest/reports/ if it does not exist). If report_path is absent from session.json, skip writing.
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.
- 2d ago First seen · 9 lines · 0 tokens per session scan A f525444d5ff8
summary is a command published in the GitHub repository avansaber/tailtest (10 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 101 tokens. 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
deploy
Command "deploy" from PraveenJayaprakash-JP/repomemory, covering deployment workflow, 1. pre-deploy checks, 2. build verification, 3. environment validation and 4. deployment steps (platform detection).
review-codex
Adversarial security review via OpenAI model — second opinion from a different AI.
sessions
Generate implementation session prompts from a PRD or research doc.
health
Command "health" from Vimalk0703/shipworthy, covering part 1: plugin installation health and part 2: project health.
refactor
Safely refactor code with test verification.
validate
Command "validate" from Vimalk0703/shipworthy, covering /validate — pre-push validation gate, what this does, steps, when to run and output format.