agentmods.dev

to-spec

to-spec is a skill for Claude Code from asteasolutions/ai-toolkit. It costs 51 tokens per session (562 once invoked), scanned A, original, MIT.

A skill that turns an already settled discussion into a short written implementation plan stored in the project's work area.

In plain words
What is it for?
Use it to write or update a local plan, record the goal, outline the approach, and identify the smallest useful test seam.
Why use it?
It preserves agreed decisions and test boundaries before coding begins, without reopening the requirements discussion.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

not rated 5repo 1mo ago A scan 51 tokens original MIT

Good fit Use it to write or update a local plan, record the goal, outline the approach, and identify the smallest useful test seam.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/asteasolutions/ai-toolkit/to-spec
View source ↗ asteasolutions/ai-toolkit
Install

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.

Any agent
npx skills add asteasolutions/ai-toolkit --skill to-spec
Clone the repo
git clone --depth 1 https://github.com/asteasolutions/ai-toolkit

Made for: Claude Code.

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 to-spec

README.md
[![agentmods](https://agentmods.dev/badge/skills/asteasolutions/ai-toolkit/to-spec/github.svg)](https://agentmods.dev/skills/asteasolutions/ai-toolkit/to-spec)
Your own site
<a href="https://agentmods.dev/skills/asteasolutions/ai-toolkit/to-spec"><img src="https://agentmods.dev/badge/skills/asteasolutions/ai-toolkit/to-spec/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 to-spec

Your own site · 80×15
<a href="https://agentmods.dev/skills/asteasolutions/ai-toolkit/to-spec"><img src="https://agentmods.dev/badge/skills/asteasolutions/ai-toolkit/to-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 562 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.00051 $0.00562
Opus 5.5 $0.00020 $0.00225
Sonnet 5.5 $0.00010 $0.00112
Haiku 4.5 $0.00005 $0.00056

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

Security

Grade A, and why

to-spec 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.

.claude/skills/setup/templates/to-spec/SKILL.md · 53 lines

How it starts

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

to-spec

Turn settled conversation into a thin Plan. Do not interview — grilling already happened; capture what was decided.

Shapes match helm's work-tree artifacts (see helm/references/artifacts.md if present).

Publish policy

  1. Always write local under .scratch/<goal-slug>/ — this is the program counter.
  2. Also mirror to GitHub only when the user asks for GitHub, or already pointed at an issue URL/id. If docs/agents/issue-tracker.md exists, follow its GitHub conventions for that mirror.
  3. Never skip the local write. Never ask which tracker after a local-only run.

Process

  1. Orient if needed. If the touched area isn't already understood, explore it. Prefer any domain vocabulary / decision docs the repo already has; discover them — don't invent a layout.

  2. Sketch test seams. Prefer existing seams; pick the highest seam that still exercises the behaviour; minimise their number (ideal: one). Check seams with the developer before writing.

  3. Write a thin Plan into the leaf doc:

    • Undecomposed goal: .scratch/<goal-slug>/task.md
    • If Intent already exists (helm Capture), fill or replace only the ## Plan section.
    • If starting fresh, write Intent (short what+why) + Plan.

    Thin Plan contents only:

    • what / why
    • test seams (how it will be verified)
    • implementation decisions
    • behaviour-level done criteria

    No brittle file paths or code. Exception: a decision-encoding prototype (schema, type, state machine) may be inlined when the shape is the decision.

  4. Ask once about extras. After the thin Plan is written, ask whether to also include any of: user stories, out of scope, further notes (or other sections the developer names). Default is no. Add only what they pick.

  5. GitHub mirror (opt-in). If publishing to GitHub, create/update the issue from the same Plan body. Local remains source of truth for resume.

Leaf shape

# <feature title>

## Intent
<what + why>

## Plan
<what/why · test seams · implementation decisions · behaviour-level done criteria>
<!-- optional extras only if the developer asked for them -->

Read the full file on GitHub · 53 lines

Files

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.

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 · 53 lines · 51 tokens per session scan A 4f00ca8a1c0e

Subscribe to this mod's changes

to-spec is a skill published in the GitHub repository asteasolutions/ai-toolkit (5 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 562 once invoked, about $0.0002 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.

Planning
Related

to-spec compared with skills from other repositories

to-spec next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
to-specasteasolutions/ai-toolkitSkill51mo agoMITA51Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79ktodayMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill99ktodayApache-2.0A19Claude Code
systematic-debuggingobra/superpowersSkill314k4d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code
chat-pet-sprite-creationmicrosoft/vscodeSkill195ktodayMITA53Claude Code, Codex