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/voxtechnologies/transmute-framework/audit-a11ynpx skills add VoxTechnologies/transmute-framework --skill audit-a11ygit clone --depth 1 https://github.com/VoxTechnologies/transmute-frameworkWrote 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/voxtechnologies/transmute-framework/audit-a11y)<a href="https://agentmods.dev/skills/voxtechnologies/transmute-framework/audit-a11y"><img src="https://agentmods.dev/badge/skills/voxtechnologies/transmute-framework/audit-a11y.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.00086 | $0.03346 |
| Opus 5 | $0.00043 | $0.01673 |
| Sonnet 5 | $0.00017 | $0.00669 |
| Haiku 4.5 | $0.00009 | $0.00335 |
Grade A, and why
audit-a11y 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.
How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Audit — Stage 6B
Read the detailed guide at ${CLAUDE_SKILL_ROOT}/references/audit-a11y-detailed-guide.md for the complete audit procedures, teammate spawn prompts, WCAG checklist patterns, and report templates.
Lead a multi-agent accessibility audit of the complete frontend codebase against BRD/PRD WCAG requirements. Identify violations and fix them.
Stage Sequence (recommended ordering): Stage 5B → (6A ‖ 6B (this stage) ‖ 6C) → 6E → 6F → 6G → 6D → 6H → 6V → 6R → 6P/6P-R → 7 (Deploy). Note: 6A, 6B, and 6C run in parallel (each in a separate session). If running in parallel, commit 6A changes as soon as 6A completes to avoid config file conflicts — see CLAUDE.md § "Stage 6 ordering".
Prerequisite Checks
Before any audit work, verify:
- Check that
./plancasting/_audits/implementation-completeness/report.mdexists and shows PASS or CONDITIONAL PASS. If missing, STOP: "Stage 5B report not found — run Stage 5B before starting Stage 6 audits." (Override: if the operator explicitly confirms 5B was intentionally skipped, proceed with a WARN in the report noting unverified implementation completeness.) - If 5B shows FAIL, STOP — the codebase has unresolved implementation gaps that must be fixed before accessibility auditing. If CONDITIONAL PASS, read documented Category C issues and skip accessibility auditing for those incomplete features.
- If
./plancasting/_audits/security/report.md(6A) exists, read it to understand security changes that should not be undone during accessibility fixes (e.g., CSP headers, CORS configuration). - If
./plancasting/_audits/performance/report.md(6C) exists, read it to understand performance optimizations (e.g., font loading, animation patterns, lazy loading) that should not be regressed. - Read
./CLAUDE.mdand./plancasting/tech-stack.mdfor project conventions. - Read relevant PRD sections for implementation context.
Inputs
- Codebase:
./src/(adapt paths per tech stack) - Tech Stack:
./plancasting/tech-stack.md - BRD Accessibility Requirements:
./plancasting/brd/08-non-functional-requirements.md(WCAG section). If not found, search:grep -rlE "WCAG|accessibility" ./plancasting/brd/ - BRD UX Requirements:
./plancasting/brd/11-user-experience-requirements.md - PRD Screen Specs:
./plancasting/prd/08-screen-specifications.md(accessibility annotations) - PRD Interaction Patterns:
./plancasting/prd/09-interaction-patterns.md - Project Rules:
./CLAUDE.md - Implementation Completeness:
./plancasting/_audits/implementation-completeness/report.md
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 · 164 lines · 86 tokens per session scan A 0f1e477f6bdb
audit-a11y is a skill published in the GitHub repository VoxTechnologies/transmute-framework (4 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 3,346 once invoked, about $0.0004 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
review
Reviews code changes for concrete bugs with P0-P2 prioritized findings. Uses parallel architectural and implementation reviewers, then validates findings to remove false positives. Use when reviewing a caller-supplied diff, branch, staged changes, file set, or pull request, and use fix mode with caller-supplied…
spec
Writes high-quality product specifications through codebase research, web research, a collaborative requirements interview, and independent review, then gives the user a link to the written spec. Use when planning a feature, defining requirements, revising an existing draft, or creating a spec/PRD. Accepts…
document
Generate minimal documentation through parallel agents.
red-blue-review
Use when the user asks for 红蓝对抗 / 蓝军评审 / 对抗评审 / 需求评审 (adversarial review of a requirement analysis), when the user asks to 整改/按 findings 整改 (red-team revision of the analysis per review findings, §5.5), or after a complex requirement's summary.md is delivered and the human opts in - the blue army reviews red army…
requirement-alignment
Use when analyzing a requirement/PRD (分析需求/解析需求/解析PRD/分析PRD), building state machines (画状态机), sequence diagrams (时序图), decision tables (决策表) or DDL from a spec, or resuming an interrupted requirement analysis (用户说"继续") - drives the three-level intent-alignment funnel (code evidence, registered inference, structured…
drogon-create-controller
生成 drogon 控制器代码（.h + .cc），支持 HttpSimpleController、HttpController、WebSocketController 三种类型。.