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 skills/stilero/claude-plugins/fix-issuesnpx skills add stilero/claude-plugins --skill fix-issuesgit clone --depth 1 https://github.com/stilero/claude-pluginsWhat 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.00060 | $0.01018 |
| Opus 5 | $0.00030 | $0.00509 |
| Sonnet 5 | $0.00012 | $0.00204 |
| Haiku 4.5 | $0.00006 | $0.00102 |
Grade A, and why
fix-issues 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.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Comment Fixer
Automatically processes GitHub pull request review comments and applies code fixes to address reviewer feedback.
Workflow
Follow this workflow when the user requests PR comment fixes:
1. Extract PR Information
Parse the PR number from the user's request. Accept formats like:
- "PR #1234"
- "pull request 1234"
- "#1234"
- Just the number "1234"
2. Fetch PR Details
Use GitHub CLI to get PR information:
gh pr view <PR_NUMBER> --json number,title,headRefName,repository
Extract:
headRefName: The PR branch namerepository: Owner and repo name
3. Ensure Repository Access
Check if running locally or remotely:
git rev-parse --git-dir 2>/dev/null
If this fails (not in a git repository):
- Clone the repository:
gh repo clone <OWNER>/<REPO> - Change to repository directory
If successful (already in repository):
- Verify it's the correct repository
- Continue with existing local clone
4. Checkout PR Branch
Switch to the PR branch:
git fetch origin
git checkout <BRANCH_NAME>
git pull origin <BRANCH_NAME>
5. Fetch All PR Comments
Retrieve review comments using GitHub CLI:
gh pr view <PR_NUMBER> --json reviews,comments --jq '.reviews[].comments[], .comments[]'
Parse the JSON output to extract:
- Comment body/text
- File path (if applicable)
- Line number or diff position
- Author
- Whether it's resolved or pending
6. Evaluate Comment Relevance
For each comment, determine if it's actionable:
Actionable comments (should be fixed):
- Requests for code changes (naming, formatting, refactoring)
- Bug reports or logic errors
- Suggestions for improvements
- Security or performance concerns
- Missing error handling
- Code quality issues
Non-actionable comments (skip):
- General discussion or questions already answered
- Comments marked as resolved
- Informational comments with no change request
- Compliments or approvals
When in doubt, err on the side of treating comments as actionable.
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 · 158 lines · 60 tokens per session scan A 66638526be2b
fix-issues is a skill published in the GitHub repository stilero/claude-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 1,018 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…