Borrowing it
Nothing to install: this file belongs to friedbotstudio/baseline. 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/friedbotstudio/baseline/main/.claude/skills/spec-sync/SKILL.mdgit clone --depth 1 https://github.com/friedbotstudio/baselineWrote 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/friedbotstudio/baseline/spec-sync)<a href="https://agentmods.dev/skills/friedbotstudio/baseline/spec-sync"><img src="https://agentmods.dev/badge/skills/friedbotstudio/baseline/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.
<a href="https://agentmods.dev/skills/friedbotstudio/baseline/spec-sync"><img src="https://agentmods.dev/badge/skills/friedbotstudio/baseline/spec-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 56 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00094 | $0.00802 |
| Opus 5.5 | $0.00038 | $0.00321 |
| Sonnet 5.5 | $0.00019 | $0.00160 |
| Haiku 4.5 | $0.00009 | $0.00080 |
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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
spec-sync — derive the central system spec, then have a human curate it
A project adopting the baseline has no spec archive to migrate from. Measured on this repository, 68% of governed files appear in no spec at all — and a project that never ran the spec phase has none. So the corpus is rebuilt from code, not imported.
What the machine does and what the human does is the whole design:
| Step | Owner |
|---|---|
| Scan the governed surface, cluster by directory, propose a concept map | machine |
| Confirm or edit that map | human, always |
| Materialize elements, derive edges, stamp digests, report coverage gaps | machine |
Prereq
project.json → memory.architecture_map.enabled is true and
memory.architecture_map.governed_surface declares this project's roots. An absent
surface is a named error, never a default — a fallback would model the consumer's
.claude/ and report total coverage over a surface that is not theirs.
Steps
-
Check the flag.
node .claude/skills/workspace/cli.mjs flags # gates on memory.architecture_map.enabled — read the `architecture_map:` linefalse→ stop and tell the user to enable it (and declare a governed surface) first. -
Propose the map.
node .claude/skills/workspace/cli.mjs sync --json # wraps workspace/sync.mjs -> proposeMap (propose half only; runSync is not exposed)The proposal is a starting point, not an inference to trust. Directory clustering is deliberately plain because a human edits it next.
-
Have the human confirm it — always. Present the proposed concepts via
AskUserQuestion: which clusters are real concepts, which should merge, which should split, what each is called. Concept membership is authored; this step has no skip and no--yes. An unattended run that inferred membership would undo the rule every prior decision in this lineage protects. -
Materialize what was confirmed.
runSyncwrites the confirmed concepts, derives one element per anchor, stamps digests, and returns coverage gaps. It refuses outright when no confirmation callback is supplied, and writes nothing before confirmation returns — a refused sync leaves the corpus byte-identical.
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.
- 1mo ago First seen · 73 lines · 94 tokens per session scan A 0ff4d4762b58
spec-sync is a skill published in the GitHub repository friedbotstudio/baseline (14 stars, last pushed 13d ago), licensed Apache-2.0. It adds 94 tokens to every session and 802 once invoked, about $0.0004 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-30.
Other skills, from other repositories
code-review-with-lsp
Code review with LSP-powered code intelligence. Uses MCP tools (diagnostics, hover, references, definition, symbols) for semantic code understanding, not just text grep.
i18n-check
An internationalization (i18n) check for software that supports multiple languages. It compares translation files with the text and translation keys used by the code.
vue-best-practices
A review checklist for Vue 2 and Vue 3 components, covering component names, prop declarations, TypeScript casts, API styles and complex template expressions.
gdpr-audit
GDPR compliance audit of code, plans, schemas, or IaC. Produces a findings report with article citations, severity, confidence, and fixes; flags evidence gaps. Not a substitute for a DPO/lawyer.
cognitive-walkthrough
Deep-dive usability evaluation of specific user tasks. Simulates novice user cognition step-by-step to identify learnability issues, unclear actions, and points of confusion.
owasp-ai-testing
AI trustworthiness testing using OWASP AI Testing Guide v1. Execute 32 test cases across 4 layers (Application, Model, Infrastructure, Data) with practical payloads and remediation.