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 adonai-labs/agent-runway --skill spec-creatorgit clone --depth 1 https://github.com/adonai-labs/agent-runwayWrote 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/adonai-labs/agent-runway/spec-creator)<a href="https://agentmods.dev/skills/adonai-labs/agent-runway/spec-creator"><img src="https://agentmods.dev/badge/skills/adonai-labs/agent-runway/spec-creator/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/adonai-labs/agent-runway/spec-creator"><img src="https://agentmods.dev/badge/skills/adonai-labs/agent-runway/spec-creator.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.00058 | $0.02018 |
| Opus 5 | $0.00029 | $0.01009 |
| Sonnet 5 | $0.00012 | $0.00404 |
| Haiku 4.5 | $0.00006 | $0.00202 |
Grade A, and why
spec-creator 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.
How it starts
The opening of the file, as written. The whole thing — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Creator
Creates development-ready specs using a structured, iterative workflow. This skill is a direct evolution of ticket-creator for teams that want spec-first execution while keeping ticket-creator available for ticket-first workflows.
When to Use
- Creating a new spec from a brief description
- Refining an existing markdown requirement into spec format
- Converting a ticket-style requirement into a spec-ready artifact
- User says "create spec", "define spec", "refine requirement", "prepare implementation spec"
Supported Spec Types
| Type | Description |
|---|---|
| Feature | New functionality or enhancement with user-facing impact |
| Fix | Corrective change for existing behaviour |
| Change | Behavioural or process change with moderate scope |
| Refactor | Internal technical improvement with no intended external behaviour change |
Core Principles
Apply shared policy: ../shared/caveman-skill-engineering.md
- Start with a complete draft, refine with user feedback
- Use project docs and code context silently where possible
- Balance intent and execution — capture both "why" and "how"
- Produce parseable structure for downstream agents
- Prefer filesystem-native output first — npm install flow first, marketplaces later
- Spec-first without forcing teams —
ticket-creatorremains valid for ticket-first teams - Clarity over volume — include what implementation needs, avoid design bloat
- Suggest split when scope is too broad
- Support dual entry — tickets may start from spec artifacts or directly from chat
- Escalate design intentionally — use
architectwhen complexity warrants it - Decompose implementation intentionally — avoid "single giant function" plans; define atomic responsibilities
8-Phase Workflow
Phase 0: Configuration Loading (Silent)
- Check for
.cursor/config/spec-creator.config.md - If found, use it as active configuration
- If not found, run generic mode:
codebase_scanning.enabled: falseoutput.default_destination: markdownoutput.markdown_path: .agent-runway/specs- Continue without blocking questions
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 261 lines · 58 tokens per session scan A b8b651226f41
spec-creator is a skill published in the GitHub repository adonai-labs/agent-runway (2 stars, last pushed 20d ago), licensed MIT. It adds 58 tokens to every session and 2,018 once invoked, about $0.0003 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.
Other skills, from other repositories
next-action
Use when the user wants a next-action recommendation based on current state — reads handoff/git/lessons/STATE and proposes top-3 by impact. Trigger: '/next', 'what should I do next', 'next action'. Proposes only, never executes.
pull-request-automation
Audits and improves the pull request workflow for a GitHub repository. Covers PR description templates, auto-labelling, CODEOWNERS, PR size checks, and branch protection rules. Invoked when the user asks to improve the PR process, set up PR automation, or add a PR template.
PR Description Writer
Writes clear, thorough pull request descriptions from a diff or list of changes.
andrej-karpathy
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
peon-ping-log
Log exercise reps for the Peon Trainer. Use when user says they did pushups, squats, or wants to log reps. Examples - "/peon-ping-log 25 pushups", "/peon-ping-log 30 squats", "log 50 pushups".
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.