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 skills add TrimVis/skills --skill refine-skillsgit clone --depth 1 https://github.com/TrimVis/skillsWrote 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/trimvis/skills/refine-skills)<a href="https://agentmods.dev/skills/trimvis/skills/refine-skills"><img src="https://agentmods.dev/badge/skills/trimvis/skills/refine-skills/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/skills/trimvis/skills/refine-skills"><img src="https://agentmods.dev/badge/skills/trimvis/skills/refine-skills.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.00069 | $0.00650 |
| Opus 5 | $0.00034 | $0.00325 |
| Sonnet 5 | $0.00014 | $0.00130 |
| Haiku 4.5 | $0.00007 | $0.00065 |
Grade A, and why
refine-skills 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 9d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refine Skills
A correction the user retypes at every invocation is a default missing from the skill. This mines the transcripts for those and proposes the edit.
Step 1 — Select
python3 ~/.claude/skills/refine-skills/skill-usage.py list
Show the table. Ask which skills to analyze by number, and accept all. Do not pick for the user.
Skills under ~5 episodes rarely yield a pattern. Say so and let the user decide.
Step 2 — Extract
Per selected skill, all time:
python3 ~/.claude/skills/refine-skills/skill-usage.py extract <skill>
Read the output. Do not grep it for complaint words — that finds pasted test output, not complaints.
Step 3 — Find
A finding needs two or more episodes on different days. One annoyed message is not a pattern.
Look for:
- Repeated args. The same instruction passed again and again (
--keep-alive,use a fable agent,also /commit). The strongest signal, and the easiest to fix. - Chaining. Args that name another skill (
and then /difit-open) — the skill should offer or do the next step. - Retries.
RETRIED after Nmmeans the first run did not land. - Corrections. Follow-up turns that redirect the run.
Then open the SKILL.md and confirm the gap is real. If the skill already says it and was ignored, the fix is wording or placement, not a new rule.
Confirm the fix is buildable before you propose it. A rule that reads state no tool exposes is dead on arrival, so check the CLI, the API, or the file format first. When only part of a finding is mechanizable, propose that part and say which part is not.
Ignore one-off task context (push-api-2, mock-api). That is the user steering, not the skill failing.
Step 4 — Propose
One finding at a time, worst first. For each, show:
- The finding and the episodes that support it (dates, quoted args).
- A diff against the
SKILL.md.
Ask to apply, skip, or edit. Apply the accepted diff, then move to the next finding. Never batch them.
What ships with it
1 file 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.
- 9d ago First seen · 64 lines · 69 tokens per session scan A 6c7fa30da6d6
refine-skills is a skill published in the GitHub repository TrimVis/skills (2 stars, last pushed 26d ago), licensed MIT. It adds 69 tokens to every session and 650 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…