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.
curl -O https://raw.githubusercontent.com/CorvidLabs/agent-3md/main/.cursor/commands/specsync-create-spec.mdgit clone --depth 1 https://github.com/CorvidLabs/agent-3mdWrote 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/commands/corvidlabs/agent-3md/specsync-create-spec)<a href="https://agentmods.dev/commands/corvidlabs/agent-3md/specsync-create-spec"><img src="https://agentmods.dev/badge/commands/corvidlabs/agent-3md/specsync-create-spec/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/commands/corvidlabs/agent-3md/specsync-create-spec"><img src="https://agentmods.dev/badge/commands/corvidlabs/agent-3md/specsync-create-spec.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.00000 | $0.00444 |
| Opus 5.5 | $0.00000 | $0.00178 |
| Sonnet 5.5 | $0.00000 | $0.00089 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
specsync-create-spec 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.
What it actually says
Create a new spec-sync module spec.
Arguments: $ARGUMENTS
- Remove
--minimalwherever it appears and remember that minimal mode was requested. Preserve the complete remaining text; do not tokenize it yet. - Classify the complete remaining text:
- A bare module name — a short identifier like
auth-serviceorbilling, matching^[A-Za-z0-9][A-Za-z0-9._-]*$. Use it as-is. - A free-text feature description — a sentence or phrase describing
what to build, e.g.
"I want a feature that lets users export their data as CSV". In this case, invent a short, kebab-case module name that captures the idea (e.g.csv-export). If the right name is ambiguous, ask the user to confirm or rename it before continuing. Keep the full description at hand — you'll use it in step 5.
- A bare module name — a short identifier like
- If minimal mode was requested, run:
This creates a minimal spec only (no companion files).specsync new <module-name> - Otherwise (default), run:
This creates the spec, companion files (specsync scaffold <module-name>tasks.md,requirements.md,context.md,testing.md, anddesign.mdifcompanions.designis enabled), a registry entry, and auto-detects related source files. - Open the newly created
specs/<module-name>/<module-name>.spec.mdand fill in thePurpose,Requirements, andPublic APIsections. If a free-text description was given in step 2, use it directly to draft these sections — ask clarifying questions if it's underspecified, but do not leave the sections as unfilled placeholder text. Do the same forrequirements.md(acceptance criteria) andtasks.md(initial task breakdown), if present. - Run
specsync checkto confirm the new spec passes validation.
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 · 35 lines · 0 tokens per session scan A f02ab9c3d7e9
specsync-create-spec is a command published in the GitHub repository CorvidLabs/agent-3md (1 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 444 tokens. 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.
specsync-create-spec compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| specsync-create-specCorvidLabs/agent-3md | Command | 1 | 5d ago | MIT | A | 0 | Claude Code, Cursor |
| expectyonatangross/orchestkit | Command | 299 | yesterday | MIT | A | 51 | Claude Code, Cursor |
| test-featureLykhoyda/rn-dev-agent | Command | 20 | 12d ago | MIT | A | 30 | Claude Code |
| checkjmagar/claude-homelab | Command | 87 | 1mo ago | MIT | A | 10 | Claude Code |
| carefulyonatangross/orchestkit | Command | 299 | yesterday | MIT | C | 84 | Claude Code, Cursor |
| stationcloudshipai/station | Command | 430 | 9mo ago | Apache-2.0 | A | 0 | Claude Code |
| pn-audit-apiperniemann/pnCore | Command | 0 | 5d ago | MIT | A | 44 | Claude Code, Cursor |