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 agentmods add skills/lootlog/monorepo/create-verification-skillnpx skills add lootlog/monorepo --skill create-verification-skillgit clone --depth 1 https://github.com/lootlog/monorepoWrote 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/lootlog/monorepo/create-verification-skill)<a href="https://agentmods.dev/skills/lootlog/monorepo/create-verification-skill"><img src="https://agentmods.dev/badge/skills/lootlog/monorepo/create-verification-skill.svg" alt="Measured on agentmods" 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.00051 | $0.00392 |
| Opus 5 | $0.00026 | $0.00196 |
| Sonnet 5 | $0.00010 | $0.00078 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
create-verification-skill 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 5d 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
Create a verification skill
Create .agents/skills/verify-<app>/ for one application at a time.
Interview the repository
Determine from code and configuration:
- the user-facing surface;
- the existing development command and expected URL, port, or socket;
- stable ways to drive it, preferring current browser, HTTP, CLI, or test harnesses;
- observable evidence and side effects;
- authentication, seed-data, environment, and isolation constraints.
Do not start the application. This repository assumes it already runs. Ask only for information that code, configuration, process state, and the visible application cannot provide.
Generate
Use the client's available skill-creation mechanism. In Codex, use the system skill-creator initializer. When no initializer exists, create the same SKILL.md and optional agents/openai.yaml structure directly. The generated skill must contain:
- Doctor: a read-only check that confirms the expected instance and version are reachable.
- Drive: exact selectors, routes, commands, or requests from this repository.
- Evidence: the action, resulting UI or response, and relevant side effects.
- Cleanup: only resources created by the verification run. Never kill processes by name.
- Feature map: the top three to five user-facing flows, each with entry path and observable success.
Store temporary evidence in an ignored location. Do not commit screenshots, credentials, tokens, or personal data.
Prove the skill
Validate the skill folder, run Doctor, drive one mapped feature against the existing instance, capture evidence, and execute cleanup. A generated skill that has not completed this loop is a draft.
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.
- 5d ago First seen · 37 lines · 51 tokens per session scan A 3627d4dea257
create-verification-skill is a skill published in the GitHub repository lootlog/monorepo (10 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 392 once invoked, about $0.0003 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
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
router-act
How to write end-to-end tests using createRouterAct and LinkAccordion. Use when writing or modifying tests that need to control the timing of internal Next.js requests (like prefetches) or assert on their responses. Covers the act API, fixture patterns, prefetch control via LinkAccordion, fake clocks, and avoiding…
deploy-release-test
Validate a commit-specific Next.js preview package and manually trigger the entire Next.js deployment test suite through the teste2edeployrelease.yml GitHub Actions workflow. Use only when asked to run the full deploy test suite or this workflow specifically from an internal vercel/next.js PR branch. Do not use for…
triage-ci-flake
Use when CI tests fail on main branch after PR merge, when investigating flaky test failures, or when user provides a PR URL/number to aggregate all failing tests.
ui4-convert-tests
Use when UI changes are complete and e2e tests need updating. Analyzes what changed in UI components and systematically finds/fixes affected tests.
e2e-write-visual-test
Use when writing a Playwright visual regression (screenshot comparison) test, tagging a test @visual, generating or updating baseline screenshots, running visual tests locally, or debugging a failing screenshot comparison in CI.