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 MichaelYcJo/SpecSeal --skill parity-setupgit clone --depth 1 https://github.com/MichaelYcJo/SpecSealWrote 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/michaelycjo/specseal/parity-setup)<a href="https://agentmods.dev/skills/michaelycjo/specseal/parity-setup"><img src="https://agentmods.dev/badge/skills/michaelycjo/specseal/parity-setup.svg" alt="Measured on agentmods" 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.00030 | $0.00885 |
| Opus 5 | $0.00015 | $0.00443 |
| Sonnet 5 | $0.00006 | $0.00177 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
parity-setup 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/specseal:parity-setup — turn on parity mode
Writes seal/parity.md, whose presence is the declaration that this
repository ports behavior from another codebase. That turns on three-way
judgment (policy ↔ original ↔ new code, with the original preserved when the
policy is silent) and lets the scribe agent fetch what the original does.
The implement skill asks this question once, when it first bootstraps a
repo. Use this command when the answer was no at the time, when the layout
predates the question, or when the original repo changes.
Procedure
-
Stop if it already exists. If
seal/parity.mdis present, show it and ask what should change instead of overwriting a declaration someone made. -
Find candidates for the original. Do not ask the user to type a path from memory when the machine can propose one:
- sibling directories of this repo that are git checkouts — a port usually sits beside its original
- an upstream or fork relation in
git remote -v - repos whose directory structure overlaps this one's
Present what you found with what each one is, and let the user pick or give a path. Never guess. A comparison against a guessed original proves nothing, which is worse than having no parity mode at all.
-
Read the baseline.
git -C <original> rev-parse HEAD. This is the commit the evidence ledger's coordinates will refer to, so record the SHA and the date you read it. -
Confirm the module. A port often covers one directory of a larger original (
apps/foo), not the whole repo. Ask when the original has an obvious multi-module layout. -
Policy root.
docs/policies/if present; otherwise propose it and say it will be created on first use. -
Write two files.
seal/parity.mdfromtemplates/parity.md, committed. Coordinate-trust exceptions start empty.~/.claude/specseal/parity-paths.md— the machine-local checkout path, keyed by this repo's origin remote URL so worktrees and second checkouts resolve to one entry. This never goes in the committed file: it is wrong for every other machine.
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.
- 2d ago Changed · -2 tokens per session 3a605cac103b
- 6d ago First seen · 74 lines · 32 tokens per session scan A 5716be2873fc
parity-setup is a skill published in the GitHub repository MichaelYcJo/SpecSeal (1 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 885 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…