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.
git clone --depth 1 https://github.com/opkod-france/opkod-claude-code-pluginsWrote 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/commands/opkod-france/opkod-claude-code-plugins/verify)<a href="https://agentmods.dev/commands/opkod-france/opkod-claude-code-plugins/verify"><img src="https://agentmods.dev/badge/commands/opkod-france/opkod-claude-code-plugins/verify.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.00016 | $0.00419 |
| Opus 5 | $0.00008 | $0.00210 |
| Sonnet 5 | $0.00003 | $0.00084 |
| Haiku 4.5 | $0.00002 | $0.00042 |
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.
What it actually says
Verify the Strapi v5 plugin in the current directory. Follow the strapi-plugin-dev skill.
Steps
-
Run
npx @strapi/sdk-plugin@latest verifyand capture output. -
Grep for anti-patterns across
server/src/**/*.{ts,tsx}andadmin/src/**/*.{ts,tsx}:strapi.entityService(should bestrapi.documents)strapi.query(escape hatch only)from 'formik'(should bereact-hook-form)from 'yup'(should bezod)from 'react-query'(should be@tanstack/react-queryv5)- Native
<button>,<input>,<select>inadmin/src/**/*.tsx(should be DS components) alert(,window.confirm((should beuseNotification/Dialog)
-
Validate every
server/src/content-types/*/schema.jsonhaskind,info.singularName,info.pluralName,collectionName. -
Check
package.json:strapi.kind: "plugin"is set@strapi/design-systemis^2.0.0(not an-rcversion)peerDependencies.reactdoes NOT include^17@tanstack/react-queryis v5
Output
Structured report:
- ✅ Passes
- ⚠️ Warnings (anti-patterns, file references with line numbers)
- ❌ Errors (from
verifyor missing required fields) - Suggested follow-up commands
Read-only — do NOT edit files.
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 · 39 lines · 16 tokens per session scan A bc3b72f3506b
verify is a command published in the GitHub repository opkod-france/opkod-claude-code-plugins (9 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 419 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-08-31.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.