Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/MichaelYcJo/SpecSealnpx agentmods add skills/michaelycjo/specseal/evidence-ciWrote 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-ci)<a href="https://agentmods.dev/skills/michaelycjo/specseal/evidence-ci"><img src="https://agentmods.dev/badge/skills/michaelycjo/specseal/evidence-ci/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-ci"><img src="https://agentmods.dev/badge/skills/michaelycjo/specseal/evidence-ci.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.00037 | $0.01041 |
| Opus 5 | $0.00018 | $0.00521 |
| Sonnet 5 | $0.00007 | $0.00208 |
| Haiku 4.5 | $0.00004 | $0.00104 |
Grade A, and why
evidence-ci 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/specseal:evidence-ci — put the drift check in CI
The ledger only earns its keep when something checks it without being asked. Run by hand, the check gets run right after you already remembered the coordinates — which is the moment you least need it.
This vendors evidence_check.py into the repo and writes the workflow. Both
files are committed, so CI does not depend on the plugin being installed on
any machine.
Why vendored rather than fetched
Fetch-at-run would tie every CI run to a network round trip and to whatever version the source happens to serve that day. A vendored copy makes the run deterministic and offline-safe, and puts the checker in the diff where a reviewer can see it change. The cost is that updates are a deliberate re-run of this command, not something that arrives silently.
Procedure
-
Locate the checker. It ships at
<plugin root>/skills/evidence-check/scripts/evidence_check.py. Resolve the plugin root from this skill file's own path rather than asking the user — the point of this command is that no one should need to know where the plugin lives. -
Check what already exists. If
tools/evidence_check.pyor.github/workflows/evidence-check.ymlis present, diff against what you would write and show it. Overwrite only on the user's say-so; an edited workflow may carry deliberate changes (a different path filter, a schedule, a dropped--strict). -
Vendor the checker to
tools/evidence_check.py, creatingtools/if needed. Keep the filename — the workflow's path filter names it, so that a change to the checker itself re-runs the check. -
Write the workflow to
.github/workflows/evidence-check.ymlfromtemplates/evidence-check.yml. Two things deserve a question rather than a default:--strictor not. It picks the exit code, not whether the build breaks. A coordinate whose content changed exits 1 without the flag and 2 with it, and the step fails on either, so a repo mid-migration gets no softer mode by dropping it. Strict is still the honest default — drift means nobody has re-verified, and 2 is the code a broken coordinate already uses. Making drift warn without blocking takes both halves: drop--strictso drift exits 1, and let the step accept that one 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.
- 2d ago Changed · +14 lines a8540be1645f
- 6d ago Changed b00f64f18036
- 10d ago First seen · 75 lines · 37 tokens per session scan A bdcae167e810
evidence-ci is a skill published in the GitHub repository MichaelYcJo/SpecSeal (1 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 1,041 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
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.