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-validategit 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-validate)<a href="https://agentmods.dev/skills/3062-in-zamud/knowledgine/sdd-validate"><img src="https://agentmods.dev/badge/skills/3062-in-zamud/knowledgine/sdd-validate/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-validate"><img src="https://agentmods.dev/badge/skills/3062-in-zamud/knowledgine/sdd-validate.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.00042 | $0.00492 |
| Opus 5.5 | $0.00017 | $0.00197 |
| Sonnet 5.5 | $0.00008 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
sdd-validate 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.
What it actually says
sdd-validate
Purpose
Verify that the implementation actually satisfies what was specified. Catches gaps between requirements and implementation before the review phase.
When to Use
- After completing all tasks in tasks.md
- Before creating a PR
- During implementation to check partial progress
Arguments
$ARGUMENTS: Spec ID (e.g.,KNOW-001) or path to spec directory
Step-by-Step Instructions
1. Load Acceptance Criteria
Read specs/KNOW-{NNN}-*/requirements.md and extract all acceptance criteria (AC-1, AC-2, ...).
2. Map Criteria to Tests
For each acceptance criterion:
- Search the test files for tests that exercise this criterion
- Look for test descriptions that mention the criterion or its key behavior
- If no test found, flag as UNCOVERED
3. Run Tests
pnpm test:run
4. Check Design Compliance
Compare implementation against design.md:
- Do exported interfaces match what was designed?
- Does the data flow match the described steps?
- Were key design decisions followed?
5. Generate Report
## Validation Report: KNOW-{NNN}
### Acceptance Criteria Coverage
| Criterion | Test File | Status |
| --------- | --------- | ----------------------- |
| AC-1: ... | tests/... | PASS / FAIL / UNCOVERED |
| AC-2: ... | tests/... | PASS / FAIL / UNCOVERED |
### Design Compliance
- [ ] Interfaces match design.md
- [ ] Data flow matches design.md
- [ ] Design decisions followed
### Build Status
pnpm verify: PASS / FAIL
### Coverage
pnpm test:coverage: XX% (target: 80%)
### Summary
X/Y acceptance criteria covered and passing.
Z criteria need attention.
Reference Files
docs/workflows/phase2-implementation.md— Implementation standards.ai-agents/config/review-checklist.md— Full review checklist
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 · 90 lines · 42 tokens per session scan A 9e7b1ba351d6
sdd-validate is a skill published in the GitHub repository 3062-in-zamud/knowledgine (3 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 492 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-31.
sdd-validate compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| sdd-validate3062-in-zamud/knowledgine | Skill | 3 | 3mo ago | MIT | A | 42 | Claude Code |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |