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-closegit 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-close)<a href="https://agentmods.dev/skills/3062-in-zamud/knowledgine/sdd-close"><img src="https://agentmods.dev/badge/skills/3062-in-zamud/knowledgine/sdd-close/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-close"><img src="https://agentmods.dev/badge/skills/3062-in-zamud/knowledgine/sdd-close.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.00036 | $0.00439 |
| Opus 5 | $0.00018 | $0.00219 |
| Sonnet 5 | $0.00007 | $0.00088 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
sdd-close 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-close
Purpose
Formally close a spec after its implementation has been merged. Ensures nothing is forgotten and knowledge is preserved for future work.
When to Use
- After PR is merged to
develop - After all acceptance criteria are verified as passing
- Before (or during) a release that includes the feature
Arguments
$ARGUMENTS: Spec ID (e.g.,KNOW-001)
Step-by-Step Instructions
1. Verify Completion
- Read
specs/KNOW-{NNN}-*/requirements.md - Confirm all acceptance criteria are checked off (or run
/sdd-validate) - Confirm
pnpm verifypasses ondevelopbranch
2. Update Spec Status
In requirements.md:
- Change
## Statusfromin-progressorreviewtocompleted - Add a
## Completedsection with:- Date completed
- Release version (if known, or "pending release")
- PR number
3. Capture Knowledge
Use knowledgine-capture to record:
- Key design decisions and their rationale
- Gotchas or surprises discovered during implementation
- Patterns that could be reused in future features
- Any deviations from the original design and why
4. Update Spec Index
In specs/README.md:
- Update the spec's status in the index table to
completed
5. Report
Output to user:
- Spec closed: KNOW-{NNN} — {title}
- Knowledge captured: {number} items
- Status: completed
- Next steps (if any): suggest
/releaseif ready
Reference Files
docs/workflows/phase4-release.md— Release processspecs/README.md— Spec index to update
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 · 71 lines · 36 tokens per session scan A 141abe8b1688
sdd-close is a skill published in the GitHub repository 3062-in-zamud/knowledgine (3 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 439 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…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.