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 eduwxyz/my-awesome-skills --skill verifygit clone --depth 1 https://github.com/eduwxyz/my-awesome-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/eduwxyz/my-awesome-skills/verify)<a href="https://agentmods.dev/skills/eduwxyz/my-awesome-skills/verify"><img src="https://agentmods.dev/badge/skills/eduwxyz/my-awesome-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/eduwxyz/my-awesome-skills/verify"><img src="https://agentmods.dev/badge/skills/eduwxyz/my-awesome-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.00149 | $0.01246 |
| Opus 5 | $0.00075 | $0.00623 |
| Sonnet 5 | $0.00030 | $0.00249 |
| Haiku 4.5 | $0.00015 | $0.00125 |
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 12d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 12d ago First seen · 93 lines · 149 tokens per session scan A 5871491cddd9
verify is a skill published in the GitHub repository eduwxyz/my-awesome-skills (16 stars, last pushed 3mo ago), with no licence file. It adds 149 tokens to every session and 1,246 once invoked, about $0.0007 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-30.
Other skills, from other repositories
implement
Use when an approved plan and task list exist and it is time to turn them into working, tested code — the SDD phase after analyze and before verify. Enforces TDD: a failing test comes before the code that makes it pass, one task at a time, appended to a progress ledger that survives compaction. Delegates test tooling…
run-nx-checks
Run nx format, lint, test, and build on affected or specified projects, then fix unambiguous failures.
pdlc-feature
An automated workflow for taking a new software feature from a description or requirements document through requirements, design, testing, implementation, review, and release preparation. It keeps one feature ID across the documents and requires tests before implementation.
pdlc-quality
A quality gate that runs configured coverage, end-to-end, and lint checks, compares their real results with declared targets, and creates a report for human approval.
pdlc-test-setup
A project setup workflow that finds the programming language, package manager, test framework, and available checking tools, then records verified commands in test-commands.yml. It can also create test folders and connect local hooks.
create-manual-test-instructions
Turn a ticket or requirements document into a concise QA manual-test file a non-author can follow. Invoke manually only.