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/craigcossairt/trellisWrote 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/craigcossairt/trellis/bug-report)<a href="https://agentmods.dev/commands/craigcossairt/trellis/bug-report"><img src="https://agentmods.dev/badge/commands/craigcossairt/trellis/bug-report/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/craigcossairt/trellis/bug-report"><img src="https://agentmods.dev/badge/commands/craigcossairt/trellis/bug-report.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.00050 | $0.00222 |
| Opus 5.5 | $0.00020 | $0.00089 |
| Sonnet 5.5 | $0.00010 | $0.00044 |
| Haiku 4.5 | $0.00005 | $0.00022 |
Grade A, and why
bug-report 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 20d 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
Follow the full protocol in docs/methodology/bug-protocol.md - read it now if it isn't already
in context.
Non-negotiables (details in the doc):
- Collect what/expected/actual before touching anything; ask for missing details
- Check
docs/common-gotchas.mdfor the symptom before diagnosing from scratch - DIAGNOSE → REPRODUCE → LOCATE → ROOT-CAUSE → FIX → TEST → VERIFY → REPORT → LOG (the usual order, not a script: go back a stage when a finding changes the theory; strengthen an existing test that passed despite the bug before adding a new one)
- Append the symptom / root cause / fix to
docs/common-gotchas.mdwhen done - Never claim "fixed" without verification
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.
- 20d ago Changed · +2 lines 3a3fe7e3fe9e
- 1mo ago First seen · 15 lines · 50 tokens per session scan A 9df96cc2a0b1
bug-report is a command published in the GitHub repository craigcossairt/trellis (5 stars, last pushed 13d ago), licensed MIT. It adds 50 tokens to every session and 222 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-08-31.
Other commands, from other repositories
adr-review
Run the workflow in docs/playbooks/adr-review.md. You review only — never write or rewrite the ADR for me. Check problem framing, option fairness, trade-offs and consequences, reversibility, the revisit trigger, and weak reasoning. Give pointed questions and concrete suggestions; I write the words. If it supersedes an…
milestone
Produce the next build doc. Run the workflow in docs/playbooks/milestone.md: read the active mode and current phase from PROJECT.md, find the next milestone in docs/progress.md, and write docs/milestones/ . - .md in the six-part format (Concept · ADR · Guided build · Challenges · Verify · Stretch). Respect the mode …
mode
Run the workflow in docs/playbooks/mode.md: read the current mode from PROJECT.md, confirm the trade-off of the target mode in one line, update the Mode field and Current mode: line in PROJECT.md, and confirm the new rules. Modes: guided (I write all code), collab (split), autopilot (you write it and teach). Full…
progress
Run the workflow in docs/playbooks/progress.md: read PROJECT.md, docs/progress.md, and the actual repo (trust the repo over the doc). Locate me, name concrete progress, append a dated session-log entry, propose the single next action, and check docs/learning-debt.md for anything worth pulling in. If I seem stuck…
start
Turn this freshly cloned template into my project. Run the workflow in docs/playbooks/start.md: welcome me, run a short conversational interview (idea, background, goals, mode, stack, pace), then write PROJECT.md, the design skeleton, and the roadmap in docs/progress.md, and offer to write my first milestone. Keep it…
refactor-clean
Refactor provided code for cleanliness, maintainability, and alignment with SOLID principles and modern best practices — no over-engineering.