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 helderberto/agent-skills --skill to-specgit clone --depth 1 https://github.com/helderberto/agent-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/helderberto/agent-skills/to-spec)<a href="https://agentmods.dev/skills/helderberto/agent-skills/to-spec"><img src="https://agentmods.dev/badge/skills/helderberto/agent-skills/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.
<a href="https://agentmods.dev/skills/helderberto/agent-skills/to-spec"><img src="https://agentmods.dev/badge/skills/helderberto/agent-skills/to-spec.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.00025 | $0.00707 |
| Opus 5.5 | $0.00010 | $0.00283 |
| Sonnet 5.5 | $0.00005 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00071 |
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 4d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
To Spec
Idea: $ARGUMENTS (if empty, ask for the problem and any solution ideas first).
Derive a kebab-case <slug> from the text before the first —/– (≤4 meaningful words, no command verbs or filler). Output: .specs/specs/<slug>.md. If it exists, update it in place (Recommended) or pick a new name.
Workflow
1. Explore codebase
Map current state: data models, services, API routes, frontend, tests. Note exists vs. must build. Codebase first, then docs. Unverifiable claims → flag as uncertain, never fabricate.
2. Check the branches
Never interview here. Check each branch below against the conversation and the code: settled → synthesize it. Open branches → one confirm round at most, each question with your recommended answer. Still open after that → stop with Next: /hb:grill <slug>. A domain term that settles here → call the Skill tool with domain-modeling to write it into the glossary, so spec and glossary agree.
| Branch | Key questions | Skip when |
|---|---|---|
| Scope & Surface | Where? New page or integrated? Roles? | CLI/library, no new entry points |
| Data & Concepts | Definitions, existing vs missing data | Never skip |
| Behavior | Interaction patterns, filtering, search | No user-facing behavior |
| Display | Numbers, tables, charts, exports | No UI |
| Access & Privacy | Who sees what? Sensitive data? | Single-user, no auth |
| Boundaries | Out of scope, deferred features | Never skip |
| Integration | Schema, services, external deps | Self-contained change |
Gray areas — ambiguities, contradictions, unstated assumptions — join that same round, each with a proposed resolution.
3. Design modules
Sketch modules. Favor deep modules — simple interface (1–3 entry points) hiding large implementation. Shallow signals: many 1:1 functions, callers compose multiple calls, feature changes require interface changes. Mark which modules need tests.
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.
- 4d ago First seen · 65 lines · 25 tokens per session scan A c3be38b9ede8
to-spec is a skill published in the GitHub repository helderberto/agent-skills (17 stars, last pushed 3d ago), licensed MIT. It adds 25 tokens to every session and 707 once invoked, about $0.0001 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-10-12.
Other skills, from other repositories
strapi
Expert Strapi headless CMS assistance covering content types, plugins, REST/GraphQL APIs, and custom controllers. Use when building self-hosted, customizable Node.js headless CMS backends.
meeting-notes-to-tasks
Converts unstructured meeting notes into structured, assigned, time-bounded action items. Never leave a meeting without knowing who does what by when.
task-decomposition
Breaks features into atomic, independently verifiable tasks. No task should take more than 4 hours. Unblocks parallel work and reduces integration risk.
business-case
This skill should be used when the user asks to "build the business case for this transformation," "write up the cost-benefit for this initiative," or needs scope, cost, benefit, sequencing, risk, and a specific ask pulled together into a decision-ready business case.
roadmap-builder
This skill should be used when the user asks to "build a transformation roadmap," "sequence this into now/next/later," "lay out the delivery plan," or provides a current state and an ambition that need sequencing into a phased roadmap.
benefits-map
This skill should be used when the user asks to "map the benefits for this initiative," "build a benefits dependency network," "what are we actually claiming this will deliver," or needs an approved business case's benefit claims decomposed into enablers, business changes, and benefits before a register can be built.