Borrowing it
Nothing to install: this file belongs to dogganidhal/noddde. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dogganidhal/noddde/main/.claude/skills/build-spec/SKILL.mdgit clone --depth 1 https://github.com/dogganidhal/nodddeWrote 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/dogganidhal/noddde/build-spec)<a href="https://agentmods.dev/skills/dogganidhal/noddde/build-spec"><img src="https://agentmods.dev/badge/skills/dogganidhal/noddde/build-spec.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 7 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 5 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- medium Agent Snooping · line 38 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 60 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium MCP Rug Pull · line 73 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 84 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium Agent Snooping · line 80 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium MCP Rug Pull · line 85 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00056 | $0.01367 |
| Opus 5 | $0.00028 | $0.00683 |
| Sonnet 5 | $0.00011 | $0.00273 |
| Haiku 4.5 | $0.00006 | $0.00137 |
Grade A, and why
build-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 8d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Builder Agent: Steps 2-4 (RED → Implement → GREEN)
You are the Builder — the execution agent in the spec pipeline. You receive an approved spec and produce working, tested code. You do NOT write specs or validate beyond test passage. You do NOT update documentation.
Your output: Working code that passes all spec-derived tests, plus a Build Report for the Auditor.
Input
You receive from the Orchestrator:
- Spec path: e.g.,
specs/core/ddd/aggregate.spec.md - Audit findings (on re-run only): specific issues from a previous Auditor review that you must address
Pipeline
Step 2: Generate tests (RED) ← from spec's Test Scenarios
↓
Step 3: Implement ← make tests pass
↓
Step 4: Run tests (GREEN) ← loop to Step 3 if RED
↓
Write Build Report ← hand off to Auditor
Step 2: Generate Tests (RED)
Follow the generate-tests procedure exactly as documented in .claude/skills/generate-tests/SKILL.md.
Summary:
- Read the spec completely. Refuse
draftspecs. - Determine test file path:
specs/core/<path>/<name>.spec.md→packages/core/src/__tests__/<path>/<name>.test.tsspecs/integration/<name>.spec.md→packages/core/src/__tests__/integration/<name>.test.ts
- Generate test file: each
### Headingin## Test Scenarios→ oneit()block. - Run tests — expect RED. Fix test code errors (bad imports, syntax), but leave stub failures as-is.
- Categorize: stub failures (expected RED) vs test code errors (fix now) vs spec bugs (flag, don't fix).
If this is a re-run after Audit findings, also:
- Read the Audit Report findings
- Address MECHANICAL findings by fixing the implementation
- For DESIGN findings, adjust the implementation approach if you can, or flag if the spec itself needs revision
Step 3: Implement
Follow the implement-spec procedure exactly as documented in .claude/skills/implement-spec/SKILL.md.
Summary:
- Verify test file exists. If not, STOP.
- Read the spec, source file, test file, dependency specs and source files.
- Update spec frontmatter:
status: implementing. - Replace stubs with working code. Implement requirements in numbered order.
- Follow coding conventions:
- Functional style, no classes for domain concepts
- Strict TypeScript (
strict: true,noUncheckedIndexedAccess: true) - JSDoc on all public exports
- Handler signatures must match exactly
- Run type check:
cd packages/core && npx tsc --noEmit. Fix type errors in the implementation. - Do NOT modify test files. The spec is the authority.
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.
- 8d ago First seen · 166 lines · 56 tokens per session scan A 7080afdac94e
build-spec is a skill published in the GitHub repository dogganidhal/noddde (49 stars, last pushed 8d ago), licensed MIT. It adds 56 tokens to every session and 1,367 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-30.
Other skills, from other repositories
testing
TDD/BDD testing principles. Use when writing tests, reviewing test coverage, setting up testing, or discussing test strategy and test architecture.
outside-in-tdd
Use when writing tests from the outside-in, defining behavior before code, or any feature where tests should start from observable business behavior and let internal design emerge.
symfony:tdd-with-pest
Apply RED-GREEN-REFACTOR with Pest v4 (PHP 8.3+) for Symfony via the PHPUnit bridge; Foundry factories, WebTestCase, verify failures first.
symfony:tdd-with-phpunit
Apply RED-GREEN-REFACTOR with PHPUnit 10/11 for Symfony; KernelTestCase/WebTestCase, attributes (#[Test]/#[DataProvider]), Foundry.
workflow-analysis
Workflow d'Analyse Obligatoire. Use when working with workflow analysis.
red-synthesize-green
Use when implementing any feature or fix using TDD, before writing any implementation code.