A workflow for keeping Markdown module specifications in sync with their source code. It also manages related files such as requirements, tasks, design, context, and testing notes.

Use it when creating, editing, or reviewing code in a module with a specification. It helps track requirements, work items, design decisions, and test plans.

It reduces the risk that documentation and code describe different behavior. It gives changes a defined process for updating and checking both sides.

How CorvidLabs/agent-3md configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to CorvidLabs/agent-3md. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/CorvidLabs/agent-3md/main/.claude/skills/spec-sync/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/CorvidLabs/agent-3md

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/corvidlabs/agent-3md/spec-sync/github.svg)](https://agentmods.dev/skills/corvidlabs/agent-3md/spec-sync)

Your own site

<a href="https://agentmods.dev/skills/corvidlabs/agent-3md/spec-sync"><img src="https://agentmods.dev/badge/skills/corvidlabs/agent-3md/spec-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/corvidlabs/agent-3md/spec-sync"><img src="https://agentmods.dev/badge/skills/corvidlabs/agent-3md/spec-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,049 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00078	$0.01049
Opus 5.5	$0.00031	$0.00420
Sonnet 5.5	$0.00016	$0.00210
Haiku 4.5	$0.00008	$0.00105

Measured 2mo ago against content hash da4dc22433b7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

spec-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 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.

.claude/skills/spec-sync/SKILL.md · 76 lines

How it starts

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

Spec-Sync Workflow

This project uses spec-sync for bidirectional spec-to-code validation. Specs live in specs/<module>/<module>.spec.md.

Companion files

Each canonical spec may have policy-selected companion files. Read and update the ones present; do not create empty companions only for ceremony:

tasks.md — Work items for this module. Check off tasks (- [x]) as you complete them. Add new tasks if you discover work needed.
requirements.md — Acceptance criteria and user stories. These are permanent invariants, not tasks — do not check them off. Update if requirements change.
context.md — Architectural decisions, key files, and current status. Update when you make design decisions or change what's in progress.
testing.md — Test strategy: automated test locations, manual QA checklists, and edge cases/boundary conditions.
design.md (opt-in) — Layout, component hierarchy, design tokens, and asset references. Present when companions.design is enabled in config.

Verified SDD change lifecycle (5.0)

For every meaningful source, test, public documentation, schema, or configuration change:

Run specsync change new "<intent>" --json and conduct the returned interview with the user.
Use specsync change answer <id> <question-id> <answer> --json until no questions remain.
Complete the adaptively selected artifacts and semantic deltas. Requirements use stable REQ-<module>-<number> IDs, a normative SHALL statement, and acceptance criteria.
Ask the user for the definition approval, then run specsync change approve <id>.
Run specsync change start <id> before editing implementation code.
Keep tasks and artifacts current, then run specsync change verify <id>.
Present verification evidence and ask for closing approval. Only after explicit approval, run specsync change accept <id>; archive separately with specsync change archive <id>.

Never invent or self-grant either human approval. If an approved definition changes, its digest becomes stale and must be approved again. specsync check validates canonical specs plus approved active deltas, requirement-to-test evidence, change coverage, and CI gates.

Read the full file on GitHub · 76 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.

2mo ago First seen · 76 lines · 78 tokens per session scan A da4dc22433b7

Subscribe to this mod's changes

spec-sync is a skill published in the GitHub repository CorvidLabs/agent-3md (1 stars, last pushed 5d ago), licensed MIT. It adds 78 tokens to every session and 1,049 once invoked, about $0.0003 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.

LLM Writing and docs agent-framework agents ai-agents bun file-format

spec-sync next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
spec-syncCorvidLabs/agent-3md	Skill	1	5d ago	MIT	A	78	Claude Code
front-tech-mapwanxingai/LightAgent	Skill	1.2k	10d ago	Apache-2.0	A	114	Claude Code, Codex
comparable-company-analysiswanxingai/LightAgent	Skill	1.2k	10d ago	Apache-2.0	A	46	Claude Code, Codex
财经分析工具包wanxingai/LightAgent	Skill	1.2k	10d ago	Apache-2.0	A	35	Claude Code, Codex
local-researchwanxingai/LightAgent	Skill	1.2k	10d ago	Apache-2.0	A	14	Claude Code, Codex
documentssixb-ai/sixb	Skill	134	yesterday	MIT	A	24	Claude Code, Codex
sixb-memorysixb-ai/sixb	Skill	134	yesterday	MIT	A	19	Claude Code, Codex

agent-3md: Skill for Claude Code