agentmods.dev

draft: Skill for Claude Code

.cursor/skills/refine/SKILL.md

refine is a skill for Claude Code, Cursor from heiko-braun/draft. It costs 7 tokens per session (628 once invoked), scanned A, original, Apache-2.0.

A workflow for updating an existing software specification after feedback, new information, or changed requirements. A specification is a written description of what a feature should do and how it should be accepted.

In plain words
What is it for?
Use it to refine feature specifications, review new requirements, ask focused questions, and update affected modules and acceptance criteria.
Why use it?
It helps keep a feature plan accurate as understanding changes. It also checks whether the update has become too large or affects additional parts of the project.

Skill for Claude CodeCursor

Written for Claude Code and Cursor: $ARGUMENTS substitution, but also installed under .cursor/.

This is heiko-braun/draft's own configuration. It tells Claude Code and Cursor how to work on draft itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything draft configures →

not rated 5repo 3mo ago A scan 7 tokens original Apache-2.0
View source ↗ heiko-braun/draft heiko-braun.github.io
Reuse

Borrowing it

Nothing to install: this file belongs to heiko-braun/draft. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/heiko-braun/draft/main/.cursor/skills/refine/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/heiko-braun/draft

Made for: Claude Code, Cursor.

Wrote 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.

agentmods badge for refine

README.md
[![agentmods](https://agentmods.dev/badge/skills/heiko-braun/draft/refine/github.svg)](https://agentmods.dev/skills/heiko-braun/draft/refine)
Your own site
<a href="https://agentmods.dev/skills/heiko-braun/draft/refine"><img src="https://agentmods.dev/badge/skills/heiko-braun/draft/refine/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.

agentmods 80×15 button for refine

Your own site · 80×15
<a href="https://agentmods.dev/skills/heiko-braun/draft/refine"><img src="https://agentmods.dev/badge/skills/heiko-braun/draft/refine.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 7 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 628 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00007 $0.00628
Opus 5.5 $0.00003 $0.00251
Sonnet 5.5 $0.00001 $0.00126
Haiku 4.5 $0.00001 $0.00063

Measured 2mo ago against content hash dc5d1f629585, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 2mo 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.

.cursor/skills/refine/SKILL.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Refine Existing Spec

Refine an existing specification based on new insights, feedback, or changing requirements.

Feature to refine: $ARGUMENTS

Instructions

  1. Load the existing spec from /specs/{feature}.md

    • If no spec exists for this feature, suggest using /spec instead
    • If multiple specs match, ask the user which one to refine

  2. Ask 2-3 focused refinement questions (one at a time):

    • What aspect needs refinement? (goals, criteria, approach, scope)
    • What new information or feedback has emerged?
    • Are there specific pain points with the current spec?

  3. Check scope and modularity:

    • Does the refinement keep the spec small enough for a single vertical slice?
    • If criteria are being added, does the total still stay at ~5 or fewer?
    • Does the refinement change which modules are affected? Update the "Affected Modules" section.
    • If the refinement significantly expands scope or blast radius, suggest a separate spec instead.

  4. Update the spec in place:

    • Preserve front-matter: Keep all existing front-matter fields (title, description, author). Keep status: proposed (refinements don't change status)
    • Preserve completed acceptance criteria checkboxes
    • Update goals, criteria, or approach as needed
    • Update "Affected Modules" and "Test Strategy" if the changes alter them
    • Add to "Out of Scope" if removing features
    • Add refinement notes to the "Notes" section with timestamp

  5. Show a diff summary:

    • Highlight what changed (goals, new criteria, removed items, affected modules, etc.)
    • Ask for confirmation before saving

  6. Get user confirmation before proceeding to implementation

    • If confirmed, use the implement skill with the refined spec
    • If not, ask if they want to refine further

Refinement Guidelines

  • Preserve progress: Don't uncheck completed criteria unless they're no longer valid
  • Be additive when possible: Add new criteria rather than rewriting existing ones
  • Document changes: Always add a timestamped note explaining what was refined and why
  • Validate scope: Check if refinements are expanding scope significantly - if so, suggest a new spec
  • Validate modularity: If the refinement introduces new module dependencies or widens the blast radius, flag it explicitly

Read the full file on GitHub · 66 lines

Changes

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.

  1. 2mo ago First seen · 66 lines · 7 tokens per session scan A dc5d1f629585

Subscribe to this mod's changes

refine is a skill published in the GitHub repository heiko-braun/draft (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 628 once invoked, about $0.0000 per session on Opus 5.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.

PlanningWriting and docs
Related

Other skills, from other repositories

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens