example-walkthrough

example-walkthrough is a skill for Claude Code, Codex from Enovatr-Labs/SpecRoute. It costs 75 tokens per session (878 once invoked), scanned A, original, Apache-2.0.

A guided walkthrough for building the sample project in a specification-driven development repository. It creates or checks a product brief, requirements, design, tasks, specialist assignments, prompts, and an implementation plan for a chosen feature.

In plain words
What is it for?
Use it to bootstrap or audit the worked example, demonstrate the full planning workflow, and confirm that each required artifact exists.
Why use it?
It shows contributors how the repository’s planning process fits together and reveals missing or incomplete project artifacts.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md; installed under .agents/ (shared by several agents); mentions Codex.

Good fit Use it to bootstrap or audit the worked example, demonstrate the full planning workflow, and confirm that each required artifact exists.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/enovatr-labs/specroute/example-walkthrough
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 Enovatr-Labs/SpecRoute --skill example-walkthrough
Clone the repo
git clone --depth 1 https://github.com/Enovatr-Labs/SpecRoute

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 example-walkthrough

README.md
[![agentmods](https://agentmods.dev/badge/skills/enovatr-labs/specroute/example-walkthrough/github.svg)](https://agentmods.dev/skills/enovatr-labs/specroute/example-walkthrough)
Your own site
<a href="https://agentmods.dev/skills/enovatr-labs/specroute/example-walkthrough"><img src="https://agentmods.dev/badge/skills/enovatr-labs/specroute/example-walkthrough/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 example-walkthrough

Your own site · 80×15
<a href="https://agentmods.dev/skills/enovatr-labs/specroute/example-walkthrough"><img src="https://agentmods.dev/badge/skills/enovatr-labs/specroute/example-walkthrough.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 878 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.00075 $0.00878
Opus 5 $0.00037 $0.00439
Sonnet 5 $0.00015 $0.00176
Haiku 4.5 $0.00007 $0.00088

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

Security

Grade A, and why

example-walkthrough 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 9d 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.

.agents/skills/example-walkthrough/SKILL.md · 73 lines

How it starts

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

Example Walkthrough

Builds (or audits) the worked example in examples/sample-project/ artifact-by-artifact, using the spec-driven flow as the script.

When to use

  • The worked example is missing or incomplete
  • A reviewer wants to confirm the example exercises every artifact shape
  • Demonstrating SpecRoute to a new contributor

Step 1: Pick a feature

Ask the user (or use the argument) for a generic feature name. Suggestions:

  • notification-preferences
  • file-upload-service
  • user-search
  • audit-log-export

Domain-neutral only. No financial, healthcare, or proprietary domains.

Step 2: Walk the spec-driven flow

For each step, verify the artifact exists and is complete; if not, invoke the named agent to draft it.

Step Artifact Path Agent
1 PRD (full 23-section) examples/sample-project/prds/active/user-search.md prd-author
2 Requirements examples/sample-project/specs/user-search/requirements.md spec-author
3 Design examples/sample-project/specs/user-search/design.md spec-author
4 Tasks examples/sample-project/specs/user-search/tasks.md spec-author
5 Agent roster examples/sample-project/agent-roster.md agent-roster-architect
6 Global master prompt examples/sample-project/prompts/000_GLOBAL_MASTER.md prompt-engineer
7 Phase masters examples/sample-project/prompts/phase{N}_<name>/000_MASTER_<phase>.md prompt-engineer
8 Numbered task prompts examples/sample-project/prompts/phase{N}_<name>/<NNN>_<task>.md prompt-engineer
9 Runtime ops prompts examples/sample-project/prompts/runtime/{pickup-next-task,daily-checkpoint}.md prompt-engineer
10 Implementation plan examples/sample-project/implementation-plan.md framework-docs-author
11 Project root context examples/sample-project/CLAUDE.md framework-docs-author
12 Drop-in README examples/sample-project/README.md framework-docs-author
13 Runtime layout examples/sample-project/.claude/{settings,agents,commands,hooks,agent-memory} runtime-architect

Read the full file on GitHub · 73 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. 9d ago First seen · 73 lines · 75 tokens per session scan A a1bc16c958ee

Subscribe to this mod's changes

example-walkthrough is a skill published in the GitHub repository Enovatr-Labs/SpecRoute (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 75 tokens to every session and 878 once invoked, about $0.0004 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