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 Enovatr-Labs/SpecRoute --skill example-walkthroughgit clone --depth 1 https://github.com/Enovatr-Labs/SpecRouteWrote 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/enovatr-labs/specroute/example-walkthrough)<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.
<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>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.00075 | $0.00878 |
| Opus 5.5 | $0.00030 | $0.00351 |
| Sonnet 5.5 | $0.00015 | $0.00176 |
| Haiku 4.5 | $0.00007 | $0.00088 |
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 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 — 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-preferencesfile-upload-serviceuser-searchaudit-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 |
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 First seen · 73 lines · 75 tokens per session scan A a1bc16c958ee
example-walkthrough is a skill published in the GitHub repository Enovatr-Labs/SpecRoute (3 stars, last pushed 5d ago), licensed Apache-2.0. It adds 75 tokens to every session and 878 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
agent-challenges
Agent skill for challenges - invoke with $agent-challenges.
course-storytelling
Use when lesson or course content is correct but forgettable and a concept has to LAND: profiles the learner, breaks the blocking false belief, then rebuilds it as epiphany story → named model → grounded analogy → proof → so-what. NOT outcomes, assessment or module order (that is course-builder), NOT slide visuals…
course-builder
Use when turning "I want to teach X" into a defensible course skeleton — measurable outcomes (Bloom + ABCD), assessment that proves each one, sequenced modules, and an outcome×module×assessment matrix — for a workshop, bootcamp, cohort or onboarding track. NOT making one concept land emotionally with story or analogy…
eli5
Use when a topic must be explained from zero to someone who knows nothing about it: one page, big pictures, very few words, everyday analogies, no jargon and nothing assumed. NOT the smallest in-conversation visual for someone already following (that is show-me), NOT a course with exercises (that is course-builder).
bello-config-advisor
Inspect a coding task, repository, and user preferences, then recommend one concrete Bello configuration and decide whether a separate planning pass should precede execution. Use when the user asks to choose or optimize a Bello setup before a run, from Codex, Claude Code, or another host. Do not use merely to monitor…
teach
Teach the user a new skill or concept, within this workspace.