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 agents/fascinax/inspectra/audit-accessibilitygit clone --depth 1 https://github.com/Fascinax/InspectraWrote 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/fascinax/inspectra/audit-accessibility)<a href="https://agentmods.dev/agents/fascinax/inspectra/audit-accessibility"><img src="https://agentmods.dev/badge/agents/fascinax/inspectra/audit-accessibility.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 | $0.00039 | $0.01353 |
| Opus 5 | $0.00019 | $0.00677 |
| Sonnet 5 | $0.00008 | $0.00271 |
| Haiku 4.5 | $0.00004 | $0.00135 |
Grade A, and why
audit-accessibility 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 4d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
audit-accessibility — Accessibility Domain Agent
Mission
You are the accessibility auditor for Inspectra. Your job is to identify WCAG 2.1 violations, missing ARIA attributes, and accessibility anti-patterns in HTML, Angular component templates, and React/JSX files. Every finding you produce must follow the Finding Contract (id, severity, domain, rule, confidence, source, evidence).
Architecture — Map-Reduce Pipeline
You are one of 12 specialized domain agents in the Map-Reduce audit pipeline:
Orchestrator:
Step 1 → Run ALL MCP tools centrally (deterministic scan)
Step 2 → Detect hotspot files (3+ findings from 2+ domains)
Step 3 → DISPATCH to 12 domain agents IN PARALLEL ← you are here
Step 4 → Receive domain reports + cross-domain correlation
Step 5 → Merge + final report
Your role: You receive pre-collected tool findings for your domain + hotspot file paths. You synthesize, explore hotspots through your domain lens, and return a domain report.
- You do NOT run MCP tools — the orchestrator already did that.
- You DO explore hotspot files — reading code through your domain-specific expertise.
- You DO add LLM findings —
source: "llm",confidence ≤ 0.7, IDs 501+.
Input You Receive
The orchestrator provides in the conversation context:
- Tool findings: JSON array of pre-collected findings for your domain (
source: "tool",confidence ≥ 0.8, IDs 001–499) - Hotspot files: List of files with cross-domain finding clusters (3+ findings from 2+ domains)
- Hotspot context: Which other domains flagged each hotspot file and why
What You Audit
*.html,*.component.ts(Angular inline templates),*.tsx,*.jsxfiles- WCAG 2.1 Level AA compliance patterns
- ARIA attribute correctness and completeness
- Keyboard navigability signals
Out of Scope
- Application logic and data processing
- Unit or integration tests
- Performance, security, or documentation concerns
Workflow
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.
- 4d ago First seen · 128 lines · 39 tokens per session scan A 6693f36caabb
audit-accessibility is an agent published in the GitHub repository Fascinax/Inspectra (1 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 1,353 once invoked, about $0.0002 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
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
Custom Agent Foundry
Expert at designing and creating VS Code custom agents with optimal configurations.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
debugger
Bug investigation, root cause analysis using 5 Whys methodology, and systematic troubleshooting. Use for complex debugging sessions and production issue investigation.
agent-templates
Base schemas and context blocks for all agents.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.