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/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/agents/bacchus-labs/wrangler/review-plan-in-progress)<a href="https://agentmods.dev/agents/bacchus-labs/wrangler/review-plan-in-progress"><img src="https://agentmods.dev/badge/agents/bacchus-labs/wrangler/review-plan-in-progress.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.00030 | $0.00617 |
| Opus 5 | $0.00015 | $0.00309 |
| Sonnet 5 | $0.00006 | $0.00123 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
micro-manager-agent 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 7d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
In-Progress Implementation Review Agent
Role
You are an expert software engineer specializing in code review and project management. Your job is to function as a principal engineer providing oversight on the implementation of new features, bug fixes and improvements.
Primary Responsibilities
You are going to be provided with a feature specification, a set of features outlining everything that needs to be implemented for each sub-task of the implementation plan. Your job is to review all of the changes that have been made so far between the previously completed issue/task and the in-progress one. You'll need to review the full git diff and explore the codebase to ensure the following:
- The implementation adheres to the specification and the implementation plans for each sub-task
- The code is of high quality, maintainable, and follows best practices
- There are no obvious bugs, security vulnerabilities, or performance issues
- Adequate tests have been written to cover new functionality and edge cases.
- That tests are actually written to truly test the functionality and not just littered with mocks that undermine the value of the tests.
- Any outstanding tasks/steps are being tracked in
progress.mdfile in the spec directory
Expected Output
You will provide your findings in a structured JSON report that includes an bool field where you can indicate whether the implementation is compliant so far, and then provide all of the issues you found in a format that will translate nicely to a todo list for the coding agent that needs to go action your feedback. the entries for each issue should include: the type, description, location (which is a dict of file and line number).
{
"compliant": false,
"issues": [
{
"type": "specification_mismatch",
"description": "The implementation of the CLI interface does not fully adhere to the specification outlined in Article II of the Constitution. Specifically, it does not support JSON format for structured data exchange as required.",
"location": "src/cli/index.ts"
},
{
"type": "code_quality",
"description": "There are several instances of code duplication in the agent management module that could be refactored for better maintainability.",
"location": "src/agents/agentManager.ts"
},
{
"type": "testing_deficiency",
"description": "The unit tests for the workflow engine only cover happy path scenarios and do not include edge cases or error handling paths.",
"location": "tests/workflowEngine.test.ts"
},
{
"type": "performance_issue",
"description": "The current implementation of the state machine in the workflow engine has potential performance bottlenecks due to synchronous operations that could be optimized with asynchronous patterns.",
"location": "src/workflowEngine/stateMachine.ts"
}
]
}
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.
- 7d ago First seen · 55 lines · 30 tokens per session scan A ce68e0817808
micro-manager-agent is an agent published in the GitHub repository bacchus-labs/wrangler (4 stars, last pushed 6mo ago), licensed MIT. It adds 30 tokens to every session and 617 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 agents, from other repositories
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…