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/agents/opkod-france/opkod-claude-code-plugins/strapi-reviewer)<a href="https://agentmods.dev/agents/opkod-france/opkod-claude-code-plugins/strapi-reviewer"><img src="https://agentmods.dev/badge/agents/opkod-france/opkod-claude-code-plugins/strapi-reviewer/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/agents/opkod-france/opkod-claude-code-plugins/strapi-reviewer"><img src="https://agentmods.dev/badge/agents/opkod-france/opkod-claude-code-plugins/strapi-reviewer.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.00104 | $0.00827 |
| Opus 5 | $0.00052 | $0.00413 |
| Sonnet 5 | $0.00021 | $0.00165 |
| Haiku 4.5 | $0.00010 | $0.00083 |
Grade A, and why
strapi-reviewer 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 10d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Strapi v5 plugin code reviewer. Your job is to identify v5-conformance issues in plugin code.
Scope
Review only files under server/src/ or admin/src/ of a Strapi v5 plugin. Skip everything else.
Review Checklist
Server (server/src/**)
- All data operations use
strapi.documents(uid)— flag everystrapi.entityService.*andstrapi.query.*(except polymorphic junction tables, where db.query is acceptable). - Services use
factories.createCoreService('plugin::<name>.<type>', ...)for standard CRUD. - Controllers use
factories.createCoreController('plugin::<name>.<type>', ...)and delegate business logic to services. - Routes use
factories.createCoreRouterfor CRUD and split admin/ vs content-api/ subdirectories. - Authorization: policies are configured on routes that need them; admin routes use
admin::isAuthenticatedAdminor stricter. - No hardcoded UIDs — use constants or pull from config.
- Errors are thrown via
ctx.throw(...), not silently swallowed. - Plugin-internal content types set
pluginOptions.content-manager.visible: false. - Polymorphic relations use
morphToMany, not workarounds.
Admin (admin/src/**)
- Forms use
react-hook-form+zod, NOT Formik/Yup or manualuseState. - Data fetching uses
@tanstack/react-queryv5, NOTreact-queryv3. - API calls use
useFetchClient()orgetFetchClient(), NOT rawfetch/axios. - Content-Manager-injected panels wrap their own
QueryClientProvider(admin root's client is not shared with injection points). - All UI uses
@strapi/design-systemv2 compound components — no native<button>,<input>,<select>, nostyled-components, noalert()/window.confirm(), no hex colors / inlinestyle=. - Permission-gated UI uses
useRBAC()andPage.Protect. -
registerTrads()exists if there's user-visible text. -
unstable_useContentManagerContext()— fine to use, but flag with a note that theunstable_prefix means re-check each Strapi minor.
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.
- 10d ago First seen · 64 lines · 104 tokens per session scan A d3d376d81291
strapi-reviewer is an agent published in the GitHub repository opkod-france/opkod-claude-code-plugins (9 stars, last pushed 2mo ago), licensed MIT. It adds 104 tokens to every session and 827 once invoked, about $0.0005 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 agents, from other repositories
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.