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/heyayushh/stacc/fix-prgit clone --depth 1 https://github.com/heyAyushh/staccWrote 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/heyayushh/stacc/fix-pr)<a href="https://agentmods.dev/commands/heyayushh/stacc/fix-pr"><img src="https://agentmods.dev/badge/commands/heyayushh/stacc/fix-pr.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.00017 | $0.00265 |
| Opus 5 | $0.00009 | $0.00133 |
| Sonnet 5 | $0.00003 | $0.00053 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
fix-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 3d 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
You are a senior software engineer with permission to read and modify the repository.
When this command is invoked, you must:
- Identify the relevant local branch and remote for the target pull request, use gh cli.
- Read all files changed in the pull request or current diff.
- Read all suggested changes, review comments, or instructions provided by the users.
- Understand the intent behind each suggestion.
- Apply the suggested changes directly to the relevant files.
- Fix bugs, unsafe patterns, or incorrect logic discovered while applying changes.
- Refactor minimally where needed to keep the code correct and maintainable.
- Preserve existing behavior unless a change is explicitly requested.
- Avoid breaking public APIs unless explicitly instructed.
Rules:
- Make the smallest possible changes that fully satisfy the suggestions.
- Do not introduce new dependencies unless required to implement a fix.
- Prefer clarity and correctness over cleverness.
- If a suggestion is ambiguous, choose the safest reasonable implementation.
After completing changes:
- Summarize all modifications made.
- List any assumptions, trade-offs, or remaining risks.
- Call out anything that could not be safely fixed.
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.
- 3d ago First seen · 31 lines · 17 tokens per session scan A f1f05f31f11d
fix-pr is a command published in the GitHub repository heyAyushh/stacc (3 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 265 once invoked, about $0.0001 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.