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/shiyas1331/devkit/address-prgit clone --depth 1 https://github.com/shiyas1331/devkitWhat 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.00031 | $0.00838 |
| Opus 5 | $0.00015 | $0.00419 |
| Sonnet 5 | $0.00006 | $0.00168 |
| Haiku 4.5 | $0.00003 | $0.00084 |
Grade A, and why
address-pr 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Address PR Review Feedback — router
This is a thin dispatcher. The picker fires when there's no flag; otherwise the command parses input and delegates to a sub-command. The full pipeline lives in commands/address-pr/default.md — the canonical body that other sub-commands reference.
Response format: one short sentence on what was done, the next concrete action, terse.
Input
$ARGUMENTS
Routing rules — apply in order
1. Picker fires when no flag is present
Trigger:
$ARGUMENTSis empty, OR$ARGUMENTScontains only a PR identifier with no--*flag
Use AskUserQuestion:
question: "How do you want to address the reviewer comments?"
header: "Mode"
multiSelect: false
options:
- label: "Walk through each comment (default)"
description: "Classify, plan, walk every reviewer item with a y/n confirmation. Commits fixes, posts replies."
- label: "Dry-run (show the plan only)"
description: "Preview the classification + proposed actions without changing files or posting."
- label: "Skip bot comments"
description: "Ignore CodeRabbit, dependabot, danger, etc. Focus on human reviewers."
- label: "Auto-resolve threads after fixes"
description: "Skip the per-thread 'mark resolved?' prompt — resolves automatically once the fix lands."
If $ARGUMENTS has no PR yet, prompt: "PR? (URL, number, or branch — e.g. 409 or feat/CAT-260-foo)".
Map answer → sub-command and re-invoke:
| Choice | Re-invoke |
|---|---|
| Walk through | /devkit:address-pr <PR> (default sub-command) |
| Dry-run | /devkit:address-pr <PR> --dry-run |
| Skip bots | /devkit:address-pr <PR> --ignore-bots |
| Auto-resolve | /devkit:address-pr <PR> --auto-resolve |
For advanced combos (--reviewer=<login>, --ignore-bots --auto-resolve), the user types the full command or invokes --help.
2. Help token → delegate to help sub-command
Trigger: $ARGUMENTS contains --help, -h, or ? as a standalone token.
Delegate to commands/address-pr/help.md.
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 · 85 lines · 31 tokens per session scan A b07ef82af29d
address-pr is a command published in the GitHub repository shiyas1331/devkit (4 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 838 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.