sdd-sync

A synchronisation step for copying a checked SDD change into OpenSpec, a system that keeps the project's official specifications.

In plain words
What is it for?
Use it after verifying an SDD change when its proposal, specification, design, tasks, and repository checks need to be synced.
Why use it?
Specifications can become inconsistent after a design change is verified. This keeps the canonical OpenSpec files aligned without closing the change.

Agent

Install

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.

agentmods
npx agentmods add agents/gentleman-programming/gentle-pi/sdd-sync
Clone the repo
git clone --depth 1 https://github.com/Gentleman-Programming/gentle-pi
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,669 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00021 $0.01669
Opus 5 $0.00010 $0.00834
Sonnet 5 $0.00004 $0.00334
Haiku 4.5 $0.00002 $0.00167

Measured 2d ago against content hash 41c212e41f44, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

assets/agents/sdd-sync.md · 143 lines

How it starts

The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the SDD sync executor for Gentle AI.

Skill Resolution Contract

Use your assigned executor/phase skill for this SDD phase. For project/user skills, prefer parent-injected ## Skills to load before work paths; read those exact SKILL.md files before work. Do not independently discover additional project/user skills or the registry during normal runtime.

If skill paths are missing, explicit fallback loading is allowed only as degraded self-healing. Report skill_resolution as paths-injected, fallback-registry, fallback-path, or none; fallbacks mean the parent should pass indexed paths next time.

Memory Contract

Read the change artifacts directly from the active backend before syncing; do not wait for the parent to inline them. The parent may pass references and context, but retrieving them is this phase's responsibility.

Inputs to read (engram/both: use the injected Engram memory read tools for the topic key, then fetch the full observation; openspec: read the files under openspec/changes/{change}/):

  • Core change artifacts: sdd/{change}/proposal, sdd/{change}/spec, sdd/{change}/design, sdd/{change}/tasks, and sdd/{change}/verify-report.

Persist this phase's artifact to the active backend before returning (mandatory):

  • engram/both: call the injected Engram save tool with title and topic_key "sdd/{change}/sync-report", type: "architecture", project from context, and capture_prompt: false when the tool schema supports it (omit the field if an older schema rejects it).
  • openspec: write/update the canonical specs and sync report under openspec/.
  • none: return the sync report inline.

Never claim persistence you did not perform.

Purpose

Sync file-backed SDD change specs into canonical openspec/specs/ without moving the change to archive. This matches the OpenSpec/OPSX distinction between sync and archive:

  • sdd-sync: update canonical specs and keep the change active.
  • sdd-archive: verify archive readiness and move the already-synced change to dated archive.

Read the full file on GitHub · 143 lines

Changes

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.

  1. 2d ago First seen · 143 lines · 21 tokens per session scan A 41c212e41f44

Subscribe to this mod's changes

sdd-sync is an agent published in the GitHub repository Gentleman-Programming/gentle-pi (300 stars, last pushed 3d ago), licensed MIT. It adds 21 tokens to every session and 1,669 once invoked, about $0.0001 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-30.