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/bacchus-labs/wrangler/audit-sessiongit clone --depth 1 https://github.com/bacchus-labs/wranglerWrote 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/bacchus-labs/wrangler/audit-session)<a href="https://agentmods.dev/commands/bacchus-labs/wrangler/audit-session"><img src="https://agentmods.dev/badge/commands/bacchus-labs/wrangler/audit-session.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 | $0.00020 | $0.03043 |
| Opus 5 | $0.00010 | $0.01522 |
| Sonnet 5 | $0.00004 | $0.00609 |
| Haiku 4.5 | $0.00002 | $0.00304 |
Grade A, and why
audit-session 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 5d 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 — 491 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wrangler Session Audit
You are conducting a comprehensive session audit to identify where wrangler's skills, tooling, and governance framework failed to prevent problems or deliver expected results.
Context
This command is used when:
- An implementation went off the rails despite following (or claiming to follow) wrangler workflows
- User suspects processes weren't followed correctly
- User wants to understand why expected safeguards didn't catch problems
- User wants to identify gaps in wrangler's skills/tooling to improve the system
Your Mission
Analyze the current session and any subsessions to identify:
- Process deviations - Where did execution deviate from expected wrangler workflows?
- Enforcement failures - Where did safeguards fail to prevent problems?
- Skill connection failures - Where did user prompts fail to trigger appropriate skills?
- Quality gate bypasses - Where were quality gates missing or bypassed?
- Testing failures - Where did testing strategy fail to catch bugs?
- Verification failures - Where were verification steps skipped or inadequate?
- Documentation gaps - Where did skills/docs fail to guide correct behavior?
What to Analyze
1. Session Structure Analysis
Examine:
- Main session conversation flow
- Subsessions created via Task tool (check for their transcripts/outputs)
- Task handoffs and checkpoints
- Completion claims and their timing
- Evidence provided (or lack thereof)
2. Skill Invocation Analysis
Check:
- Which skills were announced/used
- Which skills SHOULD have been used but weren't
- Whether skill invocation happened at appropriate times
- Whether skills were bypassed or rationalized away
- Whether skill instructions were actually followed
3. Workflow Compliance Analysis
Verify:
- TDD workflow (RED-GREEN-REFACTOR)
- Verification workflow (evidence requirements)
- Code review workflow
- Manual testing workflow
- Spec compliance verification
- Quality gate enforcement
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.
- 5d ago First seen · 491 lines · 20 tokens per session scan A 77120ec0966e
audit-session is a command published in the GitHub repository bacchus-labs/wrangler (4 stars, last pushed 6mo ago), licensed MIT. It adds 20 tokens to every session and 3,043 once invoked, about $0.0001 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.