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 woliveiras/geremmyas --skill verifygit clone --depth 1 https://github.com/woliveiras/geremmyasWrote 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/woliveiras/geremmyas/verify)<a href="https://agentmods.dev/skills/woliveiras/geremmyas/verify"><img src="https://agentmods.dev/badge/skills/woliveiras/geremmyas/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/woliveiras/geremmyas/verify"><img src="https://agentmods.dev/badge/skills/woliveiras/geremmyas/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.00037 | $0.00396 |
| Opus 5 | $0.00018 | $0.00198 |
| Sonnet 5 | $0.00007 | $0.00079 |
| Haiku 4.5 | $0.00004 | $0.00040 |
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 9d 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.
What it actually says
Verify
Do not claim completion from confidence, inspection, compilation alone, or stale output. Collect fresh evidence at the boundary affected by the change.
Procedure
- Derive the required checks from the request, acceptance criteria, changed files, risk, and repository commands.
- Run the focused test or reproduction for the changed behavior.
- Run the nearest relevant suite and static checks when practical.
- Exercise error paths, regression coverage, and observable runtime behavior required by the acceptance criteria. A build alone does not prove behavior.
- Record command, exit code, concise result, and evidence path. Keep failures separate from passing checks and distinguish preexisting failures.
- Remove temporary logs, harnesses, and instrumentation.
- Reconcile
tasks.md,plan.md, required docs, and lifecycle state. - After evidence passes, load the independent review contract only when the change's risk or governing contract requires review.
- If a required check cannot run, record its owner, reason, residual risk, and whether it blocks local completion.
Evidence record
scope: behavior or acceptance criterion
command: exact command
result: pass | fail | unavailable (exit code and concise output)
freshness: run in this verification wave
evidence: test, log, screenshot, or artifact path
residual: unavailable or subjective checks and owner
Use rationalization checks only when someone proposes skipping or weakening evidence. Never treat review as a substitute for execution evidence, or execution evidence as a substitute for required review.
What ships with it
2 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.
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.
- 9d ago First seen · 43 lines · 37 tokens per session scan A 0c7c153daa3d
verify is a skill published in the GitHub repository woliveiras/geremmyas (10 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 396 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
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.