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/amondnet/vercel-action/fix-issuegit clone --depth 1 https://github.com/amondnet/vercel-actionWhat 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.00060 |
| Opus 5 | $0.00000 | $0.00030 |
| Sonnet 5 | $0.00000 | $0.00012 |
| Haiku 4.5 | $0.00000 | $0.00006 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- fix-issue — 100% identical, 3 lines differ
What it actually says
Find and fix issue #$ARGUMENTS. Follow these steps:
- Understand the issue described in the ticket
- Locate the relevant code in our codebase
- Implement a solution that addresses the root cause
- Add appropriate tests
- Prepare a concise PR description
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 · 9 lines · 0 tokens per session scan A 757ccff3ad5f
fix-issue is a command published in the GitHub repository amondnet/vercel-action (765 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 60 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-30.
Other commands, from other repositories
gen-research
Research a topic with primary sources and write an HTML article. Asks first whether to run locally (in-chat, 5-15 min) or route to the GitHub workflow (self-hosted runner, 20-45 min, deeper output).
pi-code-review
Adversarial code review via Codex — break confidence in changes, not validate them.
pi-fact-check
Fact-check content via Gemini search + Claude verification — cross-provider claim validation.
pi-ui-review
UI/UX review via Gemini — accessibility, responsive design, component structure.
pi-askall
Ask both Codex and Gemini the same question — get three perspectives with Claude synthesis.
doctor
Check the health of a KARIMO installation, identify issues, and provide actionable recommendations.