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/implement-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/implement-spec)<a href="https://agentmods.dev/skills/dogganidhal/noddde/implement-spec"><img src="https://agentmods.dev/badge/skills/dogganidhal/noddde/implement-spec/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/dogganidhal/noddde/implement-spec"><img src="https://agentmods.dev/badge/skills/dogganidhal/noddde/implement-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 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 MCP Rug Pull · line 78 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.00039 | $0.00967 |
| Opus 5.5 | $0.00016 | $0.00387 |
| Sonnet 5.5 | $0.00008 | $0.00193 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
implement-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 2mo 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Step 3: Implement the Spec (Code Only)
Turn a behavioral specification into working code. Tests already exist and are RED — your job is to make them GREEN.
Pipeline step 3 of 6. Called by the /spec orchestrator after step 2 (test generation).
Key principle: This step writes ONLY implementation code. It does NOT generate tests — that was step 2. If tests don't exist yet, stop and tell the developer to run /generate-tests first.
Step 1: Verify Prerequisites
- Read the spec at the provided path
- Check
statusisreadyorimplementing— ifdraft, ask the developer to promote it first - Check that tests exist: Look for the test file at the expected 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
- If tests don't exist: STOP. Tell the developer:
⚠️ No test file found at <expected-path>. Tests must be generated before implementation (RED-GREEN workflow). Run `/generate-tests <spec-path>` first.
Step 2: Read Everything
- Read the spec completely — all sections
- Read the source file at
source_filefrom frontmatter - Read the existing test file — understand what the tests expect
- Read dependency specs listed in
depends_on— understand input types and contracts - Read dependency source files — understand what's already implemented
- Read sample usage if relevant — search
packages/samples/src/for usage of the module
Step 3: Set Status
Update the spec frontmatter: status: implementing
Step 4: Implement
Replace throw new Error("Not implemented") stubs with working code.
Order: Implement behavioral requirements in their numbered order. Each requirement should be satisfiable independently.
Follow these conventions (from CLAUDE.md):
- Functional style: no classes for domain concepts
- Strict TypeScript:
strict: true,noUncheckedIndexedAccess: true - JSDoc on all public exports
- No decorators, no DI containers, no base classes for domain concepts
- Handler signatures must match exactly:
- Decide handlers:
(command, state, infrastructure) => Event | Event[] | Promise<Event | Event[]> - Evolve handlers:
(event.payload, state) => newState— pure, sync - Event handlers:
(event.payload, infrastructure) => void | Promise<void> - Saga handlers:
(event, state, infrastructure & CQRSInfrastructure) => SagaReaction | Promise<SagaReaction> - Query handlers:
(query.payload, infrastructure) => Result | Promise<Result> - Projection reducers:
(event, view) => view | Promise<view>
- Decide handlers:
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.
- 2mo ago First seen · 97 lines · 39 tokens per session scan A d5855bf1ee7c
implement-spec is a skill published in the GitHub repository dogganidhal/noddde (52 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 967 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
cratis-chronicle-client-typescript
Use when connecting a standalone Node.js process to Chronicle or diagnosing its decorators, discovery or client lifecycle. Not for React generated proxies or another language's client.
cratis-arc-command-typescript
Use when bootstrapping an Arc Node.js server or defining its TypeScript commands. Not for frontend proxy consumption, validation-only changes or server queries; use the corresponding Arc sibling.
cratis-arc-query-typescript
Use when declaring Arc Node.js read-model queries or observable endpoints. Not for React proxy consumption, server commands or Chronicle event materialization.
cratis-arc-validation-typescript
Use when adding rejection rules, state checks or validation assertions to an Arc Node.js server. Not for defining commands or queries, C# and JVM validators, or append-time uniqueness.
cqrs-event-sourcing-architect
CQRS pattern, event stores, projections, eventual consistency. Activate on: CQRS, event sourcing, event store, read model, projection, aggregate, domain event, command handler. NOT for: message broker setup (use event-driven-architecture-expert), database optimization (use data-warehouse-optimizer).
enterprise-architecture-patterns
Complete guide for enterprise architecture patterns including domain-driven design, event sourcing, CQRS, saga patterns, API gateway, service mesh, and scalability.