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-statusgit 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-status)<a href="https://agentmods.dev/skills/3062-in-zamud/knowledgine/sdd-status"><img src="https://agentmods.dev/badge/skills/3062-in-zamud/knowledgine/sdd-status/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-status"><img src="https://agentmods.dev/badge/skills/3062-in-zamud/knowledgine/sdd-status.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.00037 | $0.00442 |
| Opus 5 | $0.00018 | $0.00221 |
| Sonnet 5 | $0.00007 | $0.00088 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
sdd-status 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 11d 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-status
Purpose
Provide a quick overview of all specs and their current state. Useful at the start of a session to decide what to work on, or to check overall progress.
When to Use
- At the start of a work session
- To decide which spec to work on next
- To check if all specs are closed before a release
- When asked "what's the status of specs?"
Arguments
$ARGUMENTS(optional): Filter by status (e.g.,in-progress,draft)
Step-by-Step Instructions
-
Scan
specs/directory for allKNOW-*directories -
For each spec, read
requirements.mdto extract:- Title (from
# Requirements: {title}) - Status (from
## Status) - Number of acceptance criteria (total and checked)
- Title (from
-
Read
tasks.mdto extract:- Total tasks and completed tasks
-
Generate dashboard:
## SDD Status Dashboard
| Spec | Title | Status | AC | Tasks | Last Updated |
| -------- | ------------------ | ----------- | --- | ----- | ------------ |
| KNOW-001 | Push-based capture | in-progress | 3/5 | 6/10 | 2026-04-04 |
| KNOW-002 | TOML config | draft | 0/4 | 0/8 | 2026-04-03 |
### Summary
- Draft: 1
- In Progress: 1
- Review: 0
- Completed: 0
- Total: 2
- If filtered, show only matching specs
Reference Files
specs/README.md— Spec index (may be out of sync; dashboard reads actual files)
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.
- 11d ago First seen · 62 lines · 37 tokens per session scan A 263b87c9e07d
sdd-status is a skill published in the GitHub repository 3062-in-zamud/knowledgine (3 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 442 once invoked, about $0.0002 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.
remove
Remove a deployed framework or addon from the current workspace.