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/rshade/mcp-devtools-server/triage-issuesgit clone --depth 1 https://github.com/rshade/mcp-devtools-serverWhat 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.00367 |
| Opus 5 | $0.00000 | $0.00183 |
| Sonnet 5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
triage-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 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
Launch the Issue Triage Agent (Haiku) to categorize and prioritize GitHub issues.
Usage: /triage-issues [filter]
Filters:
- all: Triage all open issues (default)
- unlabeled: Only issues without labels
- stale: Issues inactive >90 days
- P1: Focus on high-priority issues
Example: /triage-issues unlabeled
Launch Issue Triage Agent with Haiku model to analyze and categorize GitHub issues.
Use the Task tool with:
- subagent_type: general-purpose
- model: haiku
- prompt: Follow the Issue Triage Agent guide
Task:
You are the Issue Triage Agent. Follow the guide at .claude/agents/issue-triage.md to:
-
List issues based on filter: {{FILTER:-all}}
gh issue list --repo rshade/mcp-devtools-server --state open --limit 100 -
Analyze each issue:
- Read full details with
gh issue view - Check for duplicates
- Assess priority (P0-P3)
- Determine appropriate labels
- Check if related to epics
- Read full details with
-
Apply updates:
- Add labels with
gh issue edit --add-label - Set milestones
- Comment with triage analysis
- Link related issues
- Mark stale issues
- Add labels with
-
Generate report:
- Issues processed count
- Priority breakdown
- Needs attention list
- Recommended actions
Success criteria:
- All open issues have labels
- P0/P1 issues have milestones
- Duplicates are closed
- Report is comprehensive
Return triage report with actionable recommendations.
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 · 58 lines · 0 tokens per session scan A 1e38787a836b
triage-issues is a command published in the GitHub repository rshade/mcp-devtools-server (5 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 367 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
paul:help
Show available PAUL commands and usage guide.
brooks-audit
Run a Brooks-Lint architecture audit.
paul:verify
Guide manual user acceptance testing of recently built features.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
mutate
Run mutation testing to verify test quality. Builds a custom mutation tool or uses an existing framework, runs mutations, and reports the mutation score with surviving mutants.