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-syncgit 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-sync)<a href="https://agentmods.dev/skills/3062-in-zamud/knowledgine/sdd-sync"><img src="https://agentmods.dev/badge/skills/3062-in-zamud/knowledgine/sdd-sync/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-sync"><img src="https://agentmods.dev/badge/skills/3062-in-zamud/knowledgine/sdd-sync.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.00044 | $0.00502 |
| Opus 5 | $0.00022 | $0.00251 |
| Sonnet 5 | $0.00009 | $0.00100 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
sdd-sync 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-sync
Purpose
Bridge the SDD workflow (specs/) with the Harness workflow (Plans.md). Ensures both systems stay in sync without manual duplication.
When to Use
- After creating a new spec (to populate Plans.md)
- After completing tasks in Plans.md (to update tasks.md)
- At the start of a session to sync any drift
Arguments
$ARGUMENTS(optional): Spec ID (e.g.,KNOW-001). If omitted, sync all active specs.
Step-by-Step Instructions
Spec → Plans.md (Forward Sync)
- Read
specs/KNOW-{NNN}-*/tasks.md - For each unchecked task, generate a Plans.md entry:
### KNOW-001: Push-based capture
Spec: specs/KNOW-001-push-based-capture/
- [ ] Write tests for CaptureListener interface (see design.md §Architecture)
- [ ] Implement CaptureListener (see design.md §Interface Definitions)
- [ ] Write integration tests (see requirements.md AC-1 through AC-3)
- Write or update the corresponding section in Plans.md
- Preserve any existing Plans.md content that isn't spec-related
Plans.md → Spec (Reverse Sync)
- Read Plans.md for completed tasks that reference a spec
- Find the corresponding task in
specs/KNOW-{NNN}-*/tasks.md - Check off the matching task in tasks.md
- Report any tasks completed in Plans.md but not in tasks.md (drift)
Drift Detection
Compare both directions and report discrepancies:
## Sync Report: KNOW-001
### Forward (tasks.md → Plans.md)
- 3 tasks added to Plans.md
- 0 tasks already present
### Reverse (Plans.md → tasks.md)
- 2 completions synced to tasks.md
- 0 drift detected
### Warnings
- (none)
Reference Files
docs/workflows/sdd-overview.md— How SDD and Harness relate- Plans.md — Current task tracking (managed by Harness)
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 · 79 lines · 44 tokens per session scan A e110257bad30
sdd-sync is a skill published in the GitHub repository 3062-in-zamud/knowledgine (3 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 502 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.