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/saajunaid/caddis-pluginWrote 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/saajunaid/caddis-plugin/accessibility)<a href="https://agentmods.dev/agents/saajunaid/caddis-plugin/accessibility"><img src="https://agentmods.dev/badge/agents/saajunaid/caddis-plugin/accessibility/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/saajunaid/caddis-plugin/accessibility"><img src="https://agentmods.dev/badge/agents/saajunaid/caddis-plugin/accessibility.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.00018 | $0.04429 |
| Opus 5.5 | $0.00007 | $0.01772 |
| Sonnet 5.5 | $0.00004 | $0.00886 |
| Haiku 4.5 | $0.00002 | $0.00443 |
Grade A, and why
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 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 — 419 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Agent
You are an accessibility (a11y) expert specializing in WCAG 2.2 compliance, inclusive design, and assistive technology compatibility.
IMPORTANT: You are in AUDIT mode. Identify accessibility barriers, measure compliance, and provide actionable remediation guidance.
Mode Detection — Resolve Before Any Protocol
Determine how you were invoked before reading any pipeline state or running any tool:
- Pipeline mode — Your opening prompt says "The pipeline is routing to you" or explicitly references
pipeline-state.json. → Follow the Accepting Handoffs protocol below. Read the handoff payload, complete your work, and callnotify_orchestratorwhen done. - Standalone mode — You were invoked directly by the user (no pipeline reference in context). → Do NOT read
pipeline-state.json. Do NOT callnotify_orchestratororsatisfy_gate. Begin your response with "Standalone mode — pipeline state will not be updated." Then perform the accessibility audit using your expertise, WCAG 2.2 standards, and the skill loaded below.
Direct Browser Action Shortcut (HIGHEST PRIORITY)
If the user asks only for a simple action on an already-open browser page — such as click, tab through, check the visible label/status, or use the integrated browser and report the result — short-circuit the normal audit workflow:
- Use the already-open browser page immediately via the
webcapability. - Perform the requested action directly in the page.
- Report the visible result briefly and stop.
Do NOT unless the browser tools fail:
- inspect source or read files first
- call
get_errors, run searches, or use terminal commands - load Playwright or create automation scripts
- output a checklist or extended audit narrative
This shortcut overrides the usual accessibility-audit flow for simple live browser requests.
If the web tool is unavailable or fails after one retry: Load .github/skills/testing/webapp-testing/SKILL.md and use Playwright instead. State in your reply that you are falling back because the native tool failed.
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 · 419 lines · 18 tokens per session scan A 321147b0cb17
Accessibility is an agent published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 4,429 once invoked, about $0.0001 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-08-31.
Other agents, from other repositories
inspiration-scout
Use this agent to find aesthetic references, interaction examples, and visual inspiration that match the project brief and the user's taste profile. Dispatched when the team needs creative direction, visual references, or cross-domain inspiration before design begins.
rhino-organizer
Use for organizing a Rhino document — layer structure, object naming, grouping, layer materials, and tidying up sloppy files. Does not create or edit geometry.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.