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 evidence-checkgit 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/evidence-check)<a href="https://agentmods.dev/skills/michaelycjo/specseal/evidence-check"><img src="https://agentmods.dev/badge/skills/michaelycjo/specseal/evidence-check/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/evidence-check"><img src="https://agentmods.dev/badge/skills/michaelycjo/specseal/evidence-check.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.00088 | $0.06206 |
| Opus 5 | $0.00044 | $0.03103 |
| Sonnet 5 | $0.00018 | $0.01241 |
| Haiku 4.5 | $0.00009 | $0.00621 |
Grade A, and why
evidence-check 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 — 441 lines — stays where its author put it; the contents beside it link to each section on GitHub.
evidence-check — does the ledger still point at what it claims?
Specs rot silently: code moves, the ledger's coordinates keep claiming grounds that are no longer there, and the next reader trusts them. This skill makes that rot mechanical to catch — the same way a broken test catches a regression.
A coordinate names content, never a position
path#major the enclosing unit
path#major>minor ... narrowed to the place a claim is about
Both carry a hash: path#major@3f9a2c1b, path#major>minor@a71b0e42.
A coordinate's job is to put a reader in the right logic, not to pin a line. So the address is the enclosing unit, which is stable against every edit that does not change what the unit is.
| Level | What it is | Where it comes from |
|---|---|---|
| Major | a function or class for code, a heading path for a document | ast for .py; otherwise the declaration rule below; ## A / ### B for markdown |
| Minor, optional | the statement the claim is actually about | the name it references (ast for .py), or a quoted line as a last resort |
| CLAUSE | `hooks/routing.py#parse@3f9a2c1b` | ... |
| CLAUSE | `agents/smith.md#"## Boundaries"@a71b0e42` | ... |
| CLAUSE | `hooks/gate.py#run>overlaps@5d1e7c04` | ... |
Escape a pipe inside a quoted anchor as \|, or the row splits the table it
lives in.
The rule that decides everything else
An anchor degrades to DRIFTED, never to BROKEN.
The two cost different things. BROKEN says I cannot find it, go edit the
ledger — the bookkeeping this design exists to remove. DRIFTED says it
changed, go re-read the claim — the work the ledger exists for.
So the minor level narrows what is hashed and never decides whether the row
resolves. A minor anchor that stopped matching, or that now matches several
places, means that place changed: the row widens to its major unit and reports
DRIFTED. Only the major level can be BROKEN.
That is how specific and not strict stop fighting. Precision buys a smaller hash and a row that says what it is about; it never buys a new way to fail.
What ships with it
1 file 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.
- 2d ago Changed · +67 lines d5e007f94753
- 4d ago Changed · +47 lines 8ebc698b41f3
- 5d ago Changed · +242 lines · +1 tokens per session 663744d00e17
- 9d ago First seen · 85 lines · 87 tokens per session scan A 259233f8d746
evidence-check is a skill published in the GitHub repository MichaelYcJo/SpecSeal (1 stars, last pushed today), licensed MIT. It adds 88 tokens to every session and 6,206 once invoked, about $0.0004 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.