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/bendrucker/claude/refinenpx skills add bendrucker/claude --skill refinegit clone --depth 1 https://github.com/bendrucker/claudeWrote 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/bendrucker/claude/refine)<a href="https://agentmods.dev/skills/bendrucker/claude/refine"><img src="https://agentmods.dev/badge/skills/bendrucker/claude/refine.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.00039 | $0.01393 |
| Opus 5 | $0.00019 | $0.00696 |
| Sonnet 5 | $0.00008 | $0.00279 |
| Haiku 4.5 | $0.00004 | $0.00139 |
Grade A, and why
issue:refine 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 today.
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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Refinement
Arguments
Parse $ARGUMENTS:
--type bug|feature|refactor|spike: skip type identification and read that guide directly. Default: infer the type from the description per Issue Types.--compact: force the trivial body per Section Selection. Frontmatter is always emitted. Default: size the body to the issue.
Issue Types
| Type | When to Use | Guide |
|---|---|---|
| Bug | Something is broken | bug.md |
| Feature | New capability | feature.md |
| Refactor | Internal improvement, no behavior change | refactor.md |
| Spike | Timeboxed investigation; output is a recommendation, not a shipped change | spike.md |
Workflow
Read the type guide, gather context from code and related issues, and draft the refinement following the type's structure. Write it to tmp/issue-<slug>.md and output it for approval. After approval, hand the file to the platform skill (for Linear, linear:linear), which maps the frontmatter to tracker fields and saves the body. Defer all save mechanics to that skill. On GitHub, a screenshot the body references by local path goes on gh issue create --attach, per github:attach.
Output Structure
YAML frontmatter for the metadata a tracker stores as fields, then the body below the closing ---. The body leads with the summary prose directly, under no heading.
---
title: fix connection pool exhaustion under load # sentence case, one line, no long parentheticals
type: bug # bug | feature | refactor | spike
labels: [performance, database] # optional; neutral tags
priority: high # optional; urgent | high | medium | low
relations: # optional; tracker links per relation
blocks: []
blocked-by: []
related:
- https://linear.app/acme/issue/ENG-1970
duplicate-of: []
---
The nightly export marks its run successful even when per-object retrievals
time out, so downstream jobs read a partial snapshot as if it were complete.
[Type-specific sections from guide (select, don't fill)]
## 🤖 Agent Context
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed bb6d38ee3a3d
- 3d ago First seen · 112 lines · 39 tokens per session scan A 7240358fa663
issue:refine is a skill published in the GitHub repository bendrucker/claude (16 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 1,393 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-30.
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…