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 esneiderbravo/speclaw --skill syncgit clone --depth 1 https://github.com/esneiderbravo/speclawWrote 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/esneiderbravo/speclaw/sync)<a href="https://agentmods.dev/skills/esneiderbravo/speclaw/sync"><img src="https://agentmods.dev/badge/skills/esneiderbravo/speclaw/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/esneiderbravo/speclaw/sync"><img src="https://agentmods.dev/badge/skills/esneiderbravo/speclaw/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.00000 | $0.00208 |
| Opus 5.5 | $0.00000 | $0.00083 |
| Sonnet 5.5 | $0.00000 | $0.00042 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
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.
What it actually says
sync — Promote delta specs to canonical
Update the project's canonical specifications (lawbook/specs/) with a change's
delta specs, without archiving the change. Use this when the specs should
become the source of truth but the change isn't finished (e.g. multi-PR work).
lawbook_change (action: sync) is a deterministic copy — it is blind to the code. So before
promoting, YOU reconcile the delta specs against what was actually built, so the
specs that become canonical describe reality, not just the original draft.
Read steps/01-confirm.md and do only what it says.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 17 lines · 0 tokens per session scan A c0fee17d4e38
sync is a skill published in the GitHub repository esneiderbravo/speclaw (3 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 208 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.
Other skills, from other repositories
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
issue-creator
A guide for turning unclear user feedback from text, chat excerpts, or screenshots into a focused GitHub issue, a tracked software-work item. It preserves the original request and separates evidence from information that is still unknown.
retro
CP-7 retrospective: audit checkpoints, evidence quality, action items, and harvest candidates. Closes the V-model cycle and feeds the next run. Use via /retro after ship, escalate, or significant session.
status
Surfaces the current state of work in gflow-cli. Three variants at different levels of detail: full state (status), next task only (next), active plan identity (active). All variants run scripts/dev/activeplan.py and filter its output to the requested detail level.
meeting-transcript
Process meeting recordings and notes into structured decisions, action items, and team dynamics with intelligent noise filtering.
team-brief
Generate daily team intelligence brief by cross-referencing GitHub, Linear, Slack, PostHog, meetings, and braindumps with two-way Linear sync-back.