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 marchatton/agent-skills --skill verifygit clone --depth 1 https://github.com/marchatton/agent-skillsWrote 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/marchatton/agent-skills/verify)<a href="https://agentmods.dev/skills/marchatton/agent-skills/verify"><img src="https://agentmods.dev/badge/skills/marchatton/agent-skills/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/marchatton/agent-skills/verify"><img src="https://agentmods.dev/badge/skills/marchatton/agent-skills/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.00024 | $0.01124 |
| Opus 5 | $0.00012 | $0.00562 |
| Sonnet 5 | $0.00005 | $0.00225 |
| Haiku 4.5 | $0.00002 | $0.00112 |
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 7d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify
Purpose
Provide a single, consistent way for agents to verify changes before claiming “done”.
Canonical rule
Verification is skill-only.
- Do not rely on a global
verifycommand. - Do not require other docs to define verification logic. This skill is self-contained.
When to run
Run verification for every change that alters behaviour, build outputs, tests, types, linting, packaging, CI, or UI. If you cannot verify, return NO-GO with a concrete reason and the smallest unblock request.
Procedure
0) Pick scope (don’t waste time)
- Prefer the smallest scope that covers what changed:
- single package/app if changes are local
- repo-wide only if shared libraries, configs, or multiple packages changed
- If unsure, start scoped, then widen if failures suggest shared impact.
1) Discover the available verification scripts (don’t guess)
- Identify the relevant
package.json:
- repo root for repo-wide checks
- the changed package/app directory for scoped checks
- List scripts from the relevant
package.json:
- Look for canonical script names first:
verifytest,test:unit,test:cilinttypecheck,tscbuildformat,fmt,prettier:checkcheck(sometimes bundles lint/typecheck/test)
- If none exist, search one level up/down for where scripts live (monorepo layouts vary).
If you still cannot find scripts, return NO-GO and ask for expected verification steps or for a
verifyscript to be added.
2) Run verification in this order (stop on red)
Run the best available equivalents in this order:
- Format / basic hygiene (only if a check script exists)
- Prefer
format:check/prettier:check/fmt:check - Do not run auto-format as “verification” unless explicitly requested
- Lint
- Run the repo/package lint script
- Typecheck
- Run
typecheck/tsc/ equivalent
- Tests
- Run the smallest relevant test suite:
test/test:unitfor code changes- include integration/e2e only when the repo provides it and it’s relevant
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.
- 7d ago First seen · 119 lines · 24 tokens per session scan A 62fda1221349
verify is a skill published in the GitHub repository marchatton/agent-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 24 tokens to every session and 1,124 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.
work
Deliver one maintainer-approved EmDash issue, choosing the bug-fix path for a defect and the direct implementation path for an enhancement or task.