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.
git clone --depth 1 https://github.com/matteocervelli/llmsWrote 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/matteocervelli/llms/issue-fix)<a href="https://agentmods.dev/commands/matteocervelli/llms/issue-fix"><img src="https://agentmods.dev/badge/commands/matteocervelli/llms/issue-fix/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/matteocervelli/llms/issue-fix"><img src="https://agentmods.dev/badge/commands/matteocervelli/llms/issue-fix.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00014 | $0.00538 |
| Opus 5.5 | $0.00006 | $0.00215 |
| Sonnet 5.5 | $0.00003 | $0.00108 |
| Haiku 4.5 | $0.00001 | $0.00054 |
Grade A, and why
issue-fix 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 1mo 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
Fix Bug from Issue: $ARGUMENTS
💡 Tip: For safer planning, activate Plan Mode (press Shift+Tab twice) before running this command to review the fix strategy before implementation.
Analysis Phase
!gh issue view $ARGUMENTS
!git checkout -b fix/issue-$ARGUMENTS
Use sequential-thinking-mcp to:
- Understand the bug and identify root cause
- Assess security implications (auth, input validation, data exposure)
- Plan minimal fix with performance considerations
- Identify testing strategy
Implementation Phase
Implement fix following:
- Security: Validate inputs, secure error handling, no data leaks
- Performance: Measure impact, optimize queries if needed
- Defensive: Null checks, proper error boundaries
Testing Phase
# Quality checks
!npm run lint && npm run typecheck || flake8 . && mypy .
!npm run test || pytest
Create tests for:
- Bug reproduction (verify fix works)
- Security edge cases (malicious inputs)
- Performance regression (response times)
- Integration scenarios
Validation Checkpoint
Test the fix in development and confirm:
- Original bug is resolved
- No regressions in existing functionality
- Performance impact acceptable
- Security measures working
Deploy Phase
!git add . && git commit -m "fix: resolve issue $ARGUMENTS
- Root cause: [brief description]
- Security: [input validation/auth preserved/no data exposure]
- Performance: [within SLA/optimized/no regression]
- Testing: [unit/integration/security tests added]
Fixes #$ARGUMENTS"
!git push origin fix/issue-$ARGUMENTS
!gh pr create --title "fix: issue $ARGUMENTS" --body "Security-validated bug fix with performance testing. Fixes #$ARGUMENTS"
Documentation
Update:
docs/implementation/with fix detailsdocs/developers/TROUBLESHOOTING.mdif neededdocs/architecture/docs if structural changesdocs/guides/docs if user guide changes
Final Steps
- Update @CHANGELOG.md with bug fix addition and increase versioning accordingly
- Update user documentation and publish if needed
- Monitor bug fix adoption and performance post-deployment
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.
- 1mo ago First seen · 86 lines · 14 tokens per session scan A c115cd9a2487
issue-fix is a command published in the GitHub repository matteocervelli/llms (25 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 538 once invoked, about $0.0001 per session on Opus 5.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-09-01.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
react-native
Command "react-native" from getsentry/toolkit, covering examples, also associate with a release and distribution(s), xcode build step (react-native xcode) and important notes.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.