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 3062-in-zamud/knowledgine --skill sdd-implementgit clone --depth 1 https://github.com/3062-in-zamud/knowledgineWrote 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/3062-in-zamud/knowledgine/sdd-implement)<a href="https://agentmods.dev/skills/3062-in-zamud/knowledgine/sdd-implement"><img src="https://agentmods.dev/badge/skills/3062-in-zamud/knowledgine/sdd-implement/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/3062-in-zamud/knowledgine/sdd-implement"><img src="https://agentmods.dev/badge/skills/3062-in-zamud/knowledgine/sdd-implement.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.00051 | $0.00734 |
| Opus 5 | $0.00026 | $0.00367 |
| Sonnet 5 | $0.00010 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
sdd-implement 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 10d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sdd-implement
Purpose
Execute the implementation phase of SDD by following tasks.md systematically. Ensures
each task is implemented with TDD discipline and spec compliance.
When to Use
- After spec is complete (requirements.md + design.md + tasks.md finalized)
- To resume implementation of a partially completed spec
- When picking up implementation from a handoff report
Arguments
$ARGUMENTS: Spec ID (e.g.,KNOW-001) or path to spec directory
Step-by-Step Instructions
1. Load Context
-
Read the full spec:
specs/KNOW-{NNN}-*/requirements.md— acceptance criteriaspecs/KNOW-{NNN}-*/design.md— architecture, interfacesspecs/KNOW-{NNN}-*/tasks.md— ordered task list
-
Check current progress: which tasks are already checked off?
-
If there's a handoff report, read it for additional context
2. For Each Unchecked Task
Execute the TDD cycle:
Red (Write failing test):
1. Read the task description and the relevant design.md section
2. Write a test that expresses the expected behavior
3. Run: pnpm test:run → confirm test FAILS
Green (Make it pass):
1. Write minimal code following design.md interfaces
2. Run: pnpm test:run → confirm test PASSES
3. Don't over-engineer; just satisfy the test
Refactor:
1. Clean up the implementation (if needed)
2. Run: pnpm verify → confirm everything still passes
Update Progress:
1. Check off the task in tasks.md: - [x] Task N
2. If the task was the last in a phase, run pnpm verify as a checkpoint
3. Handle Deviations
If during implementation you discover:
- Missing task: Add it to tasks.md before implementing
- Design needs change: Update design.md first, then implement
- Requirement unclear: Check requirements.md; if still unclear, ask the user
- Spec is wrong: Update the spec, then implement the correct version
4. Complete Implementation
After all tasks are checked off:
- Run
pnpm verifyone final time - Run
pnpm test:coverageto check coverage target (80%) - Update spec status to
reviewin requirements.md - Create PR against
developwith spec reference in description
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.
- 10d ago First seen · 103 lines · 51 tokens per session scan A 050627ba5711
sdd-implement is a skill published in the GitHub repository 3062-in-zamud/knowledgine (3 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 734 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
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.