A feature-specification helper that turns a natural-language idea into a structured feature document. It writes testable acceptance criteria in Given/When/Then form, where each criterion states the starting situation, action, and expected result.

Use it when starting a new feature or creating a specification in the SpecKit workflow, which moves from requirements to planning, tasks, analysis, and implementation.

It turns an informal request into a shared description that developers can plan and test. It also records edge cases and prepares the work for later implementation steps.

skill-007 — Skill for Claude Code and Codex by legendtkl: A feature-specification helper that turns a natural-language idea into…

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.

agentmods

npx agentmods add skills/legendtkl/agentic-skill-router/skill-007

Any agent

npx skills add legendtkl/agentic-skill-router --skill skill-007

Clone the repo

git clone --depth 1 https://github.com/legendtkl/agentic-skill-router

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/legendtkl/agentic-skill-router/skill-007.svg)](https://agentmods.dev/skills/legendtkl/agentic-skill-router/skill-007)

Your own site

<a href="https://agentmods.dev/skills/legendtkl/agentic-skill-router/skill-007"><img src="https://agentmods.dev/badge/skills/legendtkl/agentic-skill-router/skill-007.svg" alt="Measured on agentmods" height="20"></a>

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,957 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00037	$0.01957
Opus 5	$0.00018	$0.00979
Sonnet 5	$0.00007	$0.00391
Haiku 4.5	$0.00004	$0.00196

Measured 6d ago against content hash fdd4096903ac, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

skill-007 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 6d 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.

experiments/dci-compare/skillrouter-skills/skill-007/SKILL.md · 312 lines

How it starts

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

Feature Specification Generator

Create structured feature specifications from natural language descriptions.

SpecKit Workflow

This skill is Step 1 of 6 in the Relentless workflow:

specify → plan → tasks → analyze → implement (task by task) or relentless run --feature [FEATURE NAME] --tui

What flows to next step:

User requirements → plan will create technical approach
Routing preference → carried through all artifacts
Acceptance criteria → basis for TDD in implementation

TDD is MANDATORY

The specification MUST include testable acceptance criteria:

Every user requirement should be verifiable with tests
Test scenarios should be part of each story
Edge cases should be documented for test coverage

All acceptance criteria must be written in Given/When/Then format to enable direct test implementation.

The Job

Receive feature description from user
Confirm routing preference (Step 0)
Generate short name and feature number
Create branch and feature directory in relentless/features/NNN-feature-name/
Generate specification using template
Validate specification quality (including TDD readiness)
Save to spec.md

Step 0: Confirm Routing Preference (BEFORE generating spec)

Ask the user these specific questions:

"Which routing mode?" (free/cheap/good/genius) - Default: good
"Allow free models in fallback?" - Default: yes
"Specific harness/model preference?" - Default: auto

Record the answer in spec.md metadata:

**Routing Preference**: auto: good | allow free: yes
<!-- Options: auto: free|cheap|good|genius | allow free: yes|no | OR specific: harness/model -->

Step 1: Create Feature Structure

Run the create-new-feature script to set up the branch and directory:

.claude/skills/specify/scripts/bash/create-new-feature.sh --json "FEATURE_DESCRIPTION"

This will output JSON with:

BRANCH_NAME: e.g., "003-user-auth"
SPEC_FILE: Full path to spec.md
FEATURE_DIR: Full path to feature directory
FEATURE_NUM: e.g., "003"

Read the full file on GitHub · 312 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.

6d ago First seen · 312 lines · 37 tokens per session scan A fdd4096903ac

Subscribe to this mod's changes

skill-007 is a skill published in the GitHub repository legendtkl/agentic-skill-router (5 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 1,957 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-31.

Planning

systematic-debugging

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

obra/superpowers · 21 tokens

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

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 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

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