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/rileyhilliard/agentrc/fix-issuegit clone --depth 1 https://github.com/rileyhilliard/agentrcWhat 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.00007 | $0.00359 |
| Opus 5 | $0.00003 | $0.00179 |
| Sonnet 5 | $0.00001 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
fix-issue 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
Fetch a GitHub issue and implement a fix for it.
Arguments:
$ARGUMENTS: Required. The GitHub issue number (e.g., "123" or "#123")
Process:
-
Fetch the issue details:
gh issue view <number> --json title,body,labels,comments -
Analyze the issue:
- Understand what's being requested or what bug is reported
- Check labels for context (bug, feature, enhancement, etc.)
- Review any comments for additional context or constraints
- Identify acceptance criteria if specified
-
Explore the codebase:
- Find relevant files mentioned in the issue
- Understand the current implementation
- Identify where changes need to be made
-
Plan the fix:
- Break down the work into steps
- Consider edge cases mentioned in the issue
- Think about testing requirements
-
Implement the fix:
- Make the necessary code changes
- Follow existing code patterns and style
- Keep changes focused on the issue scope
-
Verify the fix:
- Run relevant tests
- Check that the acceptance criteria are met
- Ensure no regressions
-
Summarize what was done:
- List files changed
- Explain the approach taken
- Note any follow-up items or considerations
Do not automatically commit or create a PR. Let the user review the changes first and decide when to commit.
If the issue number is not provided or the issue cannot be found, ask for clarification.
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 · 54 lines · 7 tokens per session scan A 634e6263e4be
fix-issue is a command published in the GitHub repository rileyhilliard/agentrc (3 stars, last pushed 6mo ago), licensed MIT. It adds 7 tokens to every session and 359 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
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.