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 zekiriabd/SDD-Pro --skill a11y-localgit clone --depth 1 https://github.com/zekiriabd/SDD-ProWrote 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/zekiriabd/sdd-pro/a11y-local)<a href="https://agentmods.dev/skills/zekiriabd/sdd-pro/a11y-local"><img src="https://agentmods.dev/badge/skills/zekiriabd/sdd-pro/a11y-local/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/zekiriabd/sdd-pro/a11y-local"><img src="https://agentmods.dev/badge/skills/zekiriabd/sdd-pro/a11y-local.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 27 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 42 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00185 | $0.01720 |
| Opus 5.5 | $0.00074 | $0.00688 |
| Sonnet 5.5 | $0.00037 | $0.00344 |
| Haiku 4.5 | $0.00018 | $0.00172 |
Grade A, and why
a11y-local 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 1mo 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill — Accessibility audit local (axe-core → qa_a11y)
Mode A — hors-pipeline (VENDORED.md §Coexistence). Ce skill est un outil Tech Lead à la demande. Il ne s'auto-déclenche JAMAIS pendant
/sdd-full,/sdd-poc,/dev-runou l'agentdev-frontend: le pipeline couvre l'a11y par ingest CI (ingest_axe.pyappelé depuis.github/workflows/quality.ymlauto-généré pararch). Ce skill donne au Tech Lead le même verdict en local, avant push, en réutilisant la plomberie existante — il n'invente aucun script ni table.
Anti-derive : aucune modification du code généré (
workspace/src/). Le seul artefact écrit sur disque est le JSON axe transitoire sousworkspace/.sys/.a11y/(jamaisworkspace/{feats,us,plans,src}/). La télémétrie va dansconsole.db(tableqa_a11yexistante), lue à la demande.
Pré-conditions (STEP 0)
- Front lancé : le frontend doit tourner. Le lancer via
/sdd-serve(qui affiche l'URL réelle, ex.Frontend ▶ … → :5173). Ports défaut : Vite/React5173, Angular4200, Next/Blazor Server3000, autres → lire la sortie de/sdd-serve. - axe-core CLI dispo :
npx @axe-core/cli --version(installé à la volée vianpxsi Node présent). Si Node absent → STOP[QA_FRAMEWORK_MISSING](l'a11y reste couvert par le CI du projet ; ce skill est local-only). - FEAT connue : le numéro
{n}de la FEAT auditée (pour ranger la télémétrie dansqa_a11ysous le bon FEAT — même clé que l'ingest CI).
Si le front n'est pas joignable → STOP [NETWORK] (ne pas ingérer un scan vide
qui écraserait une télémétrie CI valide via replace_qa_auditor_for_feat).
Procédure (STEP 1-3)
STEP 1 — Scan axe-core local
mkdir -p workspace/.sys/.a11y
npx @axe-core/cli "$URL" --save workspace/.sys/.a11y/axe-report.json --exit
$URL= l'URL affichée par/sdd-serve(ou fournie par le Tech Lead).- Plusieurs pages : passer plusieurs URLs ou relancer par route ; axe agrège
en un tableau
[result, …]queingest_axe.pysait normaliser. --exitfait sortir axe en non-zéro s'il trouve des violations : ignorer ce code, c'est l'ingest qui décide du verdict contre--threshold.
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.
- 1mo ago First seen · 108 lines · 185 tokens per session scan A 7c86710c77cb
a11y-local is a skill published in the GitHub repository zekiriabd/SDD-Pro (196 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 185 tokens to every session and 1,720 once invoked, about $0.0007 per session on Opus 5.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-09-03.
Other skills, from other repositories
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
critique
Adversarial design critique of the current work — render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.