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/abians/code-recall/fix-github-issuegit clone --depth 1 https://github.com/AbianS/code-recallWhat 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.00118 |
| Opus 5 | $0.00000 | $0.00059 |
| Sonnet 5 | $0.00000 | $0.00024 |
| Haiku 4.5 | $0.00000 | $0.00012 |
Grade A, and why
fix-github-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 yesterday.
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.
This is a copy
100% identical to fix-github-issue — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Please analyze and fix the GitHub issue: $ARGUMENTS.
Follow these steps:
- Use
gh issue viewto get the issue details - Understand the problem described in the issue
- Search the codebase for relevant files
- Implement the necessary changes to fix the issue
- Write and run tests to verify the fix
- Ensure code passes linting and type checking
- Create a descriptive commit message
- Push and create a PR
Remember to use the GitHub CLI (gh) for all GitHub-related tasks.
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.
- yesterday First seen · 14 lines · 0 tokens per session scan A 13141481d65b
fix-github-issue is a command published in the GitHub repository AbianS/code-recall (4 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 118 tokens. A static security scan graded it A with 0 findings. It is 100% identical to fix-github-issue, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
refactor-function
Automated function complexity reduction using multi-agent workflow.
coder-eval-implement-plan
Implement an approved codereval plan phase by phase with risk-scaled per-phase review, then a final code review.
task-verify
PitWay: Run an inprogress task's approved verification command and persist evidence.
ng-red-team
Portable command prompt generated from skills/stress-testing-agent-changes/SKILL.md. Edit the skill, then run python tools/ng.py gen-commands; do not edit this file by hand.
milestone-status
PitWay: Show a milestone's status, contract, progress, and tasks.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.