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 verifygit 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/verify)<a href="https://agentmods.dev/skills/michaelycjo/specseal/verify"><img src="https://agentmods.dev/badge/skills/michaelycjo/specseal/verify/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/michaelycjo/specseal/verify"><img src="https://agentmods.dev/badge/skills/michaelycjo/specseal/verify.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.00097 | $0.05428 |
| Opus 5.5 | $0.00039 | $0.02171 |
| Sonnet 5.5 | $0.00019 | $0.01086 |
| Haiku 4.5 | $0.00010 | $0.00543 |
Grade A, and why
verify 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 4d 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 — 454 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Seal Test
This file is the smith's and the sealer's: the smith opens it before it hands
work back, and the sealer opens it for the conditions, the labels and the
verdicts it audits against. The orchestrator reads it too. The orchestrator's
own two acts, the broad gate and the measurement of each segment, are
skills/verify/orchestration.md, which the smith and the sealer do not open.
Each instruction below binds the party making a claim, whichever of the three
it is.
A completion claim is a mark, and a mark must be earned: a check that cannot fail proves nothing, and evidence that outlives its tree state proves less than nothing. Freshness alone accepts any green command as proof; this protocol asks more of the command.
A claim stands only when all four conditions hold.
The four conditions
1. Named before run
State the proving command before executing it, next to the claim it proves. Choosing the command after seeing what passes is how a test suite's green becomes "feature works": the mapping from claim to command is the verification, and the run only executes it.
2. Able to fail
Show the check CAN go red. For a bug fix: the reproduction failed before the change (or fails when the change is reverted). For a new test: it was observed failing against the pre-change code. A check that has never been seen red is a counterfeit seal. This is the condition generic gates skip, and the one that catches assertion-free tests, mocked-away behavior, and wrong-file test runs.
An absence claim is only as good as the search behind it
"There are no callers", "the original has no such branch", "nothing reads this column": these are claims about the whole tree, and their entire evidence is that one search did not find something. An existence claim comes with a coordinate anyone can open; an absence claim comes with nothing to open, so the cost of checking it is asymmetric and it tends to pass unread.
Condition 2 applies to the search itself: run it against a case known to be present. A pattern that finds nothing there was broken, not the tree empty. Report the command and the scope it ran over, so the next session re-runs it instead of re-inventing it.
What ships with it
14 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.
- orchestration.md 28 KB
- scripts/arm_check.py 55 KB runs code
- scripts/broad_gate.py 148 KB runs code
- scripts/coordinates.py 18 KB runs code
- scripts/deferral_check.py 9.3 KB runs code
- scripts/mutation_check.py 26 KB runs code
- scripts/pact_check.py 26 KB runs code
- scripts/payload_meter.py 38 KB runs code
- scripts/pytest_record/specseal_pytest_record.py 18 KB runs code
- scripts/seal_stamp.py 62 KB runs code
- scripts/seal-mark.txt 812 B
- scripts/session_cost.py 161 KB runs code
- scripts/test_layout.py 51 KB runs code
- scripts/unverified_check.py 75 KB runs code
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.
- 4d ago Changed e22a473433f2
- 7d ago Changed · -480 lines 374ac65d6a4e
- 11d ago Changed · +1 lines 1d39d97cca62
- 12d ago Changed · -32 lines 34c7cba40f1d
- 14d ago Changed · -56 lines 6f7e88df1c61
- 17d ago Changed · +2 lines 0b7725acf6bc
- 24d ago Changed · +16 lines db6b410b8957
- 25d ago Changed · +4 lines 5640960d5552
- 26d ago Changed · +8 lines e8220084b635
- 27d ago First seen · 991 lines · 97 tokens per session scan A 3b0c1a6bc9bc
verify is a skill published in the GitHub repository MichaelYcJo/SpecSeal (1 stars, last pushed 4d ago), licensed MIT. It adds 97 tokens to every session and 5,428 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-31.
Other skills, from other repositories
critical-code-reviewer
Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
pr-review
Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…
pr-review
Use when the user wants to deeply review a pull/merge request or a local diff — "review this PR", "grill the MR", "stress-test this diff", "deep-dive code review", "code review before merge", or when they name a PR/MR URL, number, branch, commit range (A..B/A...B), tag or SHA. Works on GitHub (gh), GitLab (glab), or a…
genshijin-review
A compact pull-request review format that writes one actionable finding per line in Japanese or English.
skill-distiller
Fetches top-rated skills from skills.sh, analyzes them, and synthesizes one token-efficient skill combining the best elements. Use when the user asks to "distill skills for X", "find and combine skills for X", "synthesize skills", "merge skills", "make a skill for X from skills.sh", "update distilled skill", or…