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/issuesgit 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/issues)<a href="https://agentmods.dev/commands/bacchus-labs/wrangler/issues"><img src="https://agentmods.dev/badge/commands/bacchus-labs/wrangler/issues.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.00008 | $0.00731 |
| Opus 5 | $0.00004 | $0.00365 |
| Sonnet 5 | $0.00002 | $0.00146 |
| Haiku 4.5 | $0.00001 | $0.00073 |
Grade A, and why
issues 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 4d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wrangler:issues
Display status summary of specifications and issues using MCP tools.
Arguments
--status(optional) — Filter by status:open,in_progress,closed,cancelled--project(optional) — Filter by project/spec name--labels(optional) — Filter by labels (comma-separated)
Instructions
- Use
issues_listMCP tool to retrieve issues with any filters - Use
issues_listwithtype: "specification"to retrieve specs - Group issues by project (linked specification)
- Calculate progress metrics
- Output formatted summary
Status Model
Wrangler uses explicit status fields (not checkbox-derived):
| Status | Meaning |
|---|---|
open |
Not yet started |
in_progress |
Currently being worked on |
closed |
Completed successfully |
cancelled |
Will not be done |
Output Format
# Project Status
## Specifications
| Spec | Status | Issues | Progress |
|------|--------|--------|----------|
| SPEC-000001-auth-system | in_progress | 5 | 2/5 (40%) |
| SPEC-000002-api-cache | open | 3 | 0/3 (0%) |
## Issues by Specification
### SPEC-000001-auth-system
| ID | Title | Status | Priority |
|----|-------|--------|----------|
| ISS-000042 | Setup database schema | closed | high |
| ISS-000043 | Implement user model | in_progress | high |
| ISS-000044 | Add validation logic | open | medium |
### Unlinked Issues
| ID | Title | Status | Priority |
|----|-------|--------|----------|
| ISS-000050 | Fix typo in readme | open | low |
## Summary
- **Specifications:** 1 in_progress, 1 open
- **Issues:** 1 closed, 1 in_progress, 4 open
- **Next up:** ISS-000044 (Add validation logic)
Progress Calculation
- Issue progress: Based on explicit status field
- Spec progress:
closed_issues / total_linked_issues
MCP Tools Used
// List all specifications
issues_list({ type: "specification" })
// List all issues
issues_list({ type: "issue" })
// Filter by status
issues_list({ status: ["open", "in_progress"] })
// Filter by project
issues_list({ project: "SPEC-000001-auth-system" })
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.
- 4d ago First seen · 120 lines · 8 tokens per session scan A a981e6000842
issues is a command published in the GitHub repository bacchus-labs/wrangler (4 stars, last pushed 6mo ago), licensed MIT. It adds 8 tokens to every session and 731 once invoked, about $0.0000 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
project-recap
Generate a visual project recap for context switching.
os-meeting
快速创建和管理AI团队会议.
workspace
Testany Workspace, 管理工作空间，成员权限，团队组织.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
triage
Triage ServiceNow incidents — list open incidents, assess priority, investigate a specific INC, or analyze trends.