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/sumimakito/roll/roll-advisornpx skills add sumimakito/roll --skill roll-advisorgit clone --depth 1 https://github.com/sumimakito/rollWrote 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/skills/sumimakito/roll/roll-advisor)<a href="https://agentmods.dev/skills/sumimakito/roll/roll-advisor"><img src="https://agentmods.dev/badge/skills/sumimakito/roll/roll-advisor.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.00032 | $0.00350 |
| Opus 5 | $0.00016 | $0.00175 |
| Sonnet 5 | $0.00006 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
roll-advisor 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
roll-advisor
Optional, gated advice after roll-resolve. Skip when advisor mode is off.
Use interactive UI for skip/apply choices when available; otherwise ask concise
text questions. Never apply advice without explicit approval.
Invariant: each suggestion must preserve the PR's original behavior and scope. If a suggestion changes what the PR accomplishes, label it goal-altering and require explicit approval before treating it as an option.
Procedure
- Inspect conflicted files, resolved hunks, and history:
git log --oneline -20 -- <file>andgit shortlog -sn -- <file>. - Identify conflict cause: hot file, weak boundary, broad PR, base churn, commit order, strategy mismatch, etc.
- Offer one up-front "ignore / skip all" choice. If chosen, drop all advice for this run.
- Suggest valid conflict-reducing actions: split PR, reorder/squash commits, narrow scope, extract contended code, switch merge/rebase strategy next time, or coordinate around base churn.
- For each suggestion, state how it preserves the original goal.
- Apply only approved suggestions. Otherwise continue with the existing resolution; advice is non-blocking.
Stop Rules
- Do not edit before approval.
- Do not present behavior-changing work as normal advice.
- Do not re-ask after the user skips all advice.
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 · 35 lines · 32 tokens per session scan A 72e70d6e298f
roll-advisor is a skill published in the GitHub repository sumimakito/roll (2 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 350 once invoked, about $0.0002 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…