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 rsmdt/the-startup --skill specify-incrementalgit clone --depth 1 https://github.com/rsmdt/the-startupWrote 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/rsmdt/the-startup/specify-incremental)<a href="https://agentmods.dev/skills/rsmdt/the-startup/specify-incremental"><img src="https://agentmods.dev/badge/skills/rsmdt/the-startup/specify-incremental/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/rsmdt/the-startup/specify-incremental"><img src="https://agentmods.dev/badge/skills/rsmdt/the-startup/specify-incremental.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.01179 |
| Opus 5.5 | $0.00021 | $0.00472 |
| Sonnet 5.5 | $0.00011 | $0.00236 |
| Haiku 4.5 | $0.00005 | $0.00118 |
Grade A, and why
specify-incremental 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona
Act as an implementation planning specialist that breaks a single-feature specification into executable phases following TDD principles. Plans enable a developer to work independently without requiring clarification.
Every plan answers four questions: WHAT produces value (deliverables, not activities), IN WHAT ORDER do tasks execute (dependencies and sequencing), HOW TO VALIDATE correctness (test-first approach), and WHERE is each task specified (links to requirements.md / solution.md sections).
Spec Target: $ARGUMENTS
Interface
Task { id: string // T1.1, T1.2, T2.1, ... description: string ref?: string // Solution/Section + line range activity?: string // domain-modeling, backend-api, frontend-ui, ... parallel?: boolean prime: string // what to read before starting test: string // what to test (red) implement: string // what to build (green) validate: string // how to verify (refactor) }
Phase { number: number title: string file: string // plan/phase-N.md status: pending | in_progress | completed tasks: Task[] }
State { specDirectory = "" requirements = "" // path to requirements.md solution = "" // path to solution.md planDirectory = "" // path to plan/ subdirectory phases: Phase[] }
Constraints
Always:
- Every task produces a verifiable deliverable — not just an activity.
- All requirements.md acceptance criteria map to specific tasks.
- All solution.md components have corresponding implementation tasks.
- Dependencies are explicit with no circular dependencies.
- Every task follows TDD: Prime, Test, Implement, Validate.
- Follow template structure exactly — preserve all sections as defined.
- Wait for user confirmation before proceeding to next phase.
- Write each phase to a separate plan/phase-N.md file.
- Keep plan/README.md as the manifest with phase links and checklist.
- All tasks trace back to requirements.md or solution.md.
- Parallel tasks can actually run independently.
- Leave the
plan/README.mdphases checklist in the exact format- [ ] [Phase N: Title](phase-N.md)— this format is parsed by the implement-incremental skill for phase discovery and status tracking.
What ships with it
15 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.
- evals/evals.json 2.4 KB
- evals/fixtures/spec-single-feature/requirements.md 896 B
- evals/fixtures/spec-single-feature/solution.md 1.3 KB
- evals/fixtures/spec-validation-gaps/plan/phase-1.md 549 B
- evals/fixtures/spec-validation-gaps/plan/phase-2.md 221 B
- evals/fixtures/spec-validation-gaps/plan/README.md 418 B
- evals/fixtures/spec-validation-gaps/requirements.md 205 B
- evals/fixtures/spec-validation-gaps/solution.md 181 B
- examples/output-example.md 471 B
- examples/phase-examples.md 6.7 KB
- reference/output-format.md 418 B
- reference/task-structure.md 2.9 KB
- template.md 5.7 KB
- templates/phase.md 1.8 KB
- validation.md 4.0 KB
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 · 135 lines · 53 tokens per session scan A 3bda06e6b87d
specify-incremental is a skill published in the GitHub repository rsmdt/the-startup (569 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 1,179 once invoked, about $0.0002 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-30.
Other skills, from other repositories
mutation-campaign-configuration
Use when the user mentions mewt, muton, or mutation testing and asks to initialize, scope, estimate, configure, validate, or optimize a campaign before execution. Writes only the TOML config and validates readiness without generating mutants or touching source. Not for running the campaign: use mewt run separately.
spec-driven
Use when starting a project or feature, requirements are unclear, or a change crosses modules. Produces an approved six-area spec, plan, tasks, and an offensive-first TDD implementation. Not for implementation from existing specs — use spec-driven-implementation.
tdd
Use when asked to develop a fix or feature test-first, plan a multi-step TDD build, or work red-to-green in slices. Writes attacks before implementation, probes the suite with mutations, and advances one vertical slice at a time. Not for hardening existing code without a change; use tests-adversarial. Not for deleting…
mutation-triage-genotoxic
Use when a mutation campaign has produced surviving mutants that need triage. Classifies each mutant as false-positive, missing-test, genotoxic, or removable using a coverage map, and proposes which tests to write or dead code to remove. Not for configuring or running campaigns: use mutation-campaign-configuration.
tdd
Use when implementing features or bug fixes test-first.
maid-methodology
Provides guidance on the MAID (Manifest-driven AI Development) methodology including creating manifests, writing behavioral tests, implementing code with TDD, validation, and using MAID subagents. Use when the user mentions MAID, manifests, manifest-driven development, task manifests, behavioral tests, or validation…