skill-011

skill-011 is a skill for Claude Code, Codex from legendtkl/agentic-skill-router. It costs 40 tokens per session (1,615 once invoked), scanned A, original, MIT.

A guided conversation process for turning a rough idea into a written design or specification. It asks one question at a time and ends with a design document rather than an implementation.

In plain words
What is it for?
It is for refining ideas before implementation, designing new features, planning behavior changes, and preparing complex refactors.
Why use it?
It helps clarify purpose, constraints, success criteria, and exclusions before work begins. This reduces uncertainty about what a new feature or refactor should do.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

Good fit It is for refining ideas before implementation, designing new features, planning behavior changes, and preparing complex refactors.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/legendtkl/agentic-skill-router/skill-011
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 legendtkl/agentic-skill-router --skill skill-011
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.

agentmods badge for skill-011

README.md
[![agentmods](https://agentmods.dev/badge/skills/legendtkl/agentic-skill-router/skill-011.svg)](https://agentmods.dev/skills/legendtkl/agentic-skill-router/skill-011)
Your own site
<a href="https://agentmods.dev/skills/legendtkl/agentic-skill-router/skill-011"><img src="https://agentmods.dev/badge/skills/legendtkl/agentic-skill-router/skill-011.svg" alt="Measured on agentmods" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,615 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.00040 $0.01615
Opus 5 $0.00020 $0.00807
Sonnet 5 $0.00008 $0.00323
Haiku 4.5 $0.00004 $0.00161

Measured 8d ago against content hash 0479d1867e2f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

skill-011 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 8d 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-011/SKILL.md · 207 lines

How it starts

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

Brainstorming Ideas Into Designs

Overview

Turn rough ideas into a validated design/spec through short, collaborative dialogue.

Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design in small sections (200-300 words), checking after each section whether it looks right so far.

⚠️ IMPORTANT: This skill produces a design document only. Implementation is a separate step that the user decides when and how to do.

The Process

Understand the idea

  • Review current project state first (files, docs, recent commits, existing patterns)
  • Ask one question per message; if a topic needs more exploration, split it across multiple turns
  • Prefer multiple-choice questions when practical (faster to answer), but use open-ended when needed
  • Focus on purpose, constraints, success criteria, and non-goals

Interactive Questions with ask_questions Tool

MUST Use the ask_questions tool for a more interactive and efficient dialogue. This provides a native UI for the user to select options or input text.

Tool Parameters
Parameter Description
header Short label (max 12 chars) - used as identifier
question Full question text to display
options Array of 0-6 options with label and optional description
multiSelect Allow multiple selections (default: false)
allowFreeformInput Allow free text in addition to options
recommended Mark an option as recommended (never use for quizzes)
Rules
  • Maximum 4 questions per call (batch related questions)
  • "Other" option is added automatically — don't add it manually
  • Use recommended only to suggest YOUR preferred implementation choice
  • Omit options array for free text input
Example: Multiple Choice
{
  "questions": [{
    "header": "Approach",
    "question": "Which architecture approach should we use?",
    "options": [
      {"label": "Monolith", "description": "Simple, single deployment"},
      {"label": "Microservices", "description": "Scalable, complex"},
      {"label": "Modular Monolith", "description": "Best of both", "recommended": true}
    ]
  }]
}

Read the full file on GitHub · 207 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. 8d ago First seen · 207 lines · 40 tokens per session scan A 0479d1867e2f

Subscribe to this mod's changes

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

Related

Other skills, from other repositories

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

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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 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