Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mostafa-drz/claude-skillsnpx agentmods add skills/mostafa-drz/claude-skills/exploration-to-specWrote 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/mostafa-drz/claude-skills/exploration-to-spec)<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/exploration-to-spec"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/exploration-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/mostafa-drz/claude-skills/exploration-to-spec"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/exploration-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.00072 | $0.02279 |
| Opus 5.5 | $0.00029 | $0.00912 |
| Sonnet 5.5 | $0.00014 | $0.00456 |
| Haiku 4.5 | $0.00007 | $0.00228 |
Grade A, and why
exploration-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 1mo 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exploration to Spec
Convert exploration conversations into structured, professional technical documents that satisfy the needs of an entire startup product team — from PM to QA.
Preferences
On startup, use the Read tool to load ~/.claude/skills/exploration-to-spec/preferences.md. If it doesn't exist, use defaults.
Context
On startup, use Bash to detect: current git branch, repo name, and working directory. Check if ~/.claude/skills/exploration-to-spec/reference/ exists for templates.
Command routing
Check $ARGUMENTS:
help→ display help then stopconfig→ interactive setup then stopreset→ delete~/.claude/skills/exploration-to-spec/preferences.md, confirm, stop- output path provided → use as the file destination
- empty → ask where to save
Help
Exploration to Spec — Convert conversations into technical specifications
Usage:
/exploration-to-spec Interactive (asks for output path)
/exploration-to-spec ./docs/design.md Write to specific path
/exploration-to-spec --format roadmap Use roadmap template
/exploration-to-spec --format design-doc Use design document template
/exploration-to-spec --format adr Architecture Decision Record
/exploration-to-spec --format rfc Request for Comments
/exploration-to-spec --audience pm Optimize for product managers
/exploration-to-spec --audience engineering Optimize for engineers
/exploration-to-spec --audience all Full cross-functional doc (default)
/exploration-to-spec config Set preferences
/exploration-to-spec reset Clear preferences
/exploration-to-spec help This help
Examples:
/exploration-to-spec ./technical-docs/insight-engine.md
/exploration-to-spec --format roadmap --audience all ./docs/roadmap.md
/exploration-to-spec --format adr (asks for output path)
Current preferences:
(read from preferences.md)
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.
- 1mo ago Changed · +2 lines 6f1e0c1dd1e2
- 1mo ago First seen · 268 lines · 72 tokens per session scan A 1c721c339355
exploration-to-spec is a skill published in the GitHub repository mostafa-drz/claude-skills (4 stars, last pushed yesterday), licensed MIT. It adds 72 tokens to every session and 2,279 once invoked, about $0.0003 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.
Other skills, from other repositories
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
rudder-data-graphs
Produces Data Graph YAML from RETL sources for Audiences. Use when designing Data Graphs, mapping RETL to entities/events, or assessing customer fit for Audiences.
rudder-typer-workflow
Generates type-safe SDKs (Swift/Kotlin) from tracking plans with compile-time validation. Use when generating type-safe event tracking code from tracking plans using RudderTyper.
rudder-instrumentation-planning
Designs event taxonomies and instrumentation strategies from business requirements. Use when designing event taxonomy from scratch or restructuring existing instrumentation strategy.
rudder-instrumentation-debugging
Diagnoses and fixes validation errors, schema issues, and instrumentation problems. Use when debugging validation errors, schema issues, or instrumentation problems.
rudder-ai-events-verify
Verifies RudderStack AI events locally: captures what an instrumented app or MCP server sends, validates it against the AI events v0.3 schema, and checks joins, counts, identity and content. Use when testing AI events, or when AI or MCP events look wrong or missing.