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/arvoreeducacao/rhm/refinementnpx skills add arvoreeducacao/rhm --skill refinementgit clone --depth 1 https://github.com/arvoreeducacao/rhmWrote 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/arvoreeducacao/rhm/refinement)<a href="https://agentmods.dev/skills/arvoreeducacao/rhm/refinement"><img src="https://agentmods.dev/badge/skills/arvoreeducacao/rhm/refinement.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.00035 | $0.00335 |
| Opus 5 | $0.00017 | $0.00168 |
| Sonnet 5 | $0.00007 | $0.00067 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
refinement 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
Refinement
Use this skill when a task needs to be clarified before implementation — defining the problem, the contracts, and the scope.
Questions to answer
- What specific problem are we solving, in one clear and measurable sentence?
- What evidence exists that this problem is real (data, examples, complaints, incidents)?
- What happens if we do nothing?
- Who is directly impacted (user type, team, system)?
- What must this solution cover now?
- What will this solution NOT do (to avoid misinterpretation)?
Enrichment
- Are there explicit alternatives we're discarding? Why?
- Minimum expected behavior for input, processing, and output?
- Happy path for each main flow?
- Behavior on errors, network failures, timeouts, invalid input?
- Variations by user type, permission, plan, or context?
- Expected volume now and maximum to support?
- What UX, code, architecture, and accessibility standards apply?
Technical refinement
- Which repositories will be modified
- What changes are needed in each
- API contracts (endpoints, payloads, responses)
- Database changes (if any)
- Integration points between repositories
Notes
- Use database MCPs to understand current schema and data
- Ask for a Figma link if UI changes are involved
- Define contracts and high-level architecture — not code patterns
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 · 43 lines · 35 tokens per session scan A 5d3b5ef6a56d
refinement is a skill published in the GitHub repository arvoreeducacao/rhm (19 stars, last pushed 4d ago), licensed MIT. It adds 35 tokens to every session and 335 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…