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/Institut-du-Numerique-Responsable/skill-nrWrote 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/institut-du-numerique-responsable/skill-nr/accessibilite-check)<a href="https://agentmods.dev/agents/institut-du-numerique-responsable/skill-nr/accessibilite-check"><img src="https://agentmods.dev/badge/agents/institut-du-numerique-responsable/skill-nr/accessibilite-check.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.00026 | $0.00384 |
| Opus 5 | $0.00013 | $0.00192 |
| Sonnet 5 | $0.00005 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
accessibilite-check 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 8d 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
Licensed CC-BY-SA-4.0
The repository is licensed CC-BY-SA-4.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 8d ago First seen · 25 lines · 26 tokens per session scan A 27821dd16d00
accessibilite-check is an agent published in the GitHub repository Institut-du-Numerique-Responsable/skill-nr (3 stars, last pushed 10d ago), licensed CC-BY-SA-4.0. It adds 26 tokens to every session and 384 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 agents, from other repositories
frontend-reviewer
Use when reviewing changes to UI components, hooks, client state, or rendering logic (React/Vue/Svelte) — verifies component correctness, state topology, and render purity against the frontend and ui persona standards.
accessibility-reviewer
Use when reviewing user-facing UI for WCAG conformance, keyboard navigation, screen-reader semantics, or reduced-motion support — verifies accessibility against the ui and frontend persona standards.
mb-reviewer
Code review agent for /mb work review-loop. Reads stage diff + pipeline.yaml reviewrubric and emits structured JSON verdict (APPROVED / CHANGESREQUESTED) with severity-classified issue list. Drives the severity-gate decision.
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…
frontend-reviewer
Reviews a diff through the FRONTEND lens only (a11y/ARIA, semantic HTML, focus/keyboard, state handling, responsive/viewport, color-only signaling). Read-only. Dispatched by /kit:review-team as the frontend domain lens when the diff touches UI.
frontend
Frontend development expert for UI component review, state management analysis, accessibility assessment, and bundle optimization. Use when reviewing React, Vue, TypeScript, CSS, or any client-side code.