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/LarouexNonprofitConsulting/larouex-fullstack-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/commands/larouexnonprofitconsulting/larouex-fullstack-plugin/audit-accessibility)<a href="https://agentmods.dev/commands/larouexnonprofitconsulting/larouex-fullstack-plugin/audit-accessibility"><img src="https://agentmods.dev/badge/commands/larouexnonprofitconsulting/larouex-fullstack-plugin/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.1 | $0.00000 | $0.00179 |
| Opus 5 | $0.00000 | $0.00089 |
| Sonnet 5 | $0.00000 | $0.00036 |
| Haiku 4.5 | $0.00000 | $0.00018 |
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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- audit-accessibility — 100% identical, 0 lines differ
What it actually says
Audit the project for WCAG 2.1 AA accessibility compliance.
Analyze and report on:
- Semantic HTML usage (header, nav, main, article, section, footer)
- ARIA labels, roles, and attributes on interactive elements
- Keyboard navigation support (tab order, focus management, skip links)
- Color contrast ratios for text and interactive elements
- Screen reader compatibility and announcements
- Form accessibility (labels, error messages, required fields)
- Image alt text and decorative image handling
- Focus indicators on interactive elements
- Heading hierarchy (h1-h6 proper structure)
- Link text clarity (avoid "click here")
- Button vs link semantic correctness
- Mobile touch target sizes
- Motion and animation (prefers-reduced-motion)
Provide specific fixes with code examples for each issue. Test with automated tools (jest-axe, Lighthouse). Include manual testing recommendations.
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.
- 3d ago First seen · 19 lines · 0 tokens per session scan A 547d82d8734d
audit-accessibility is a command published in the GitHub repository LarouexNonprofitConsulting/larouex-fullstack-plugin (8 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 179 tokens. 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 commands, from other repositories
audit-accessibility
Audit the project for WCAG 2.1 AA accessibility compliance.
scaffold-nextjs
Scaffold a basic Next.js 15 project with modern best practices.
optimize-images
Optimize all images in the project for web performance. Convert images to modern formats (WebP, AVIF) with fallbacks. Replace img tags with Next.js Image component for automatic optimization. Add proper width/height attributes to prevent layout shift. Implement lazy loading for below-fold images. Compress existing…
optimize-lighthouse
Run Lighthouse audit and implement recommended performance fixes. Improve Core Web Vitals: Largest Contentful Paint (LCP), First Input Delay (FID), Cumulative Layout Shift (CLS). Optimize font loading with font-display: swap and preloading. Add resource hints (preload, prefetch, preconnect) for critical resources. Fix…
review-before-deploy
Execute comprehensive pre-deployment review using code-review-agent with all relevant platform agents. Run complete deployment readiness checklist: verify all tests pass (unit, integration, E2E), security audit clean (no Critical/High issues), performance benchmarks met (Lighthouse > 90), TypeScript compilation…
add-checkout
Create comprehensive shopping cart and checkout flow. Implement cart state management with Context API or Zustand. Create cart UI component with item list, quantity controls, and remove buttons. Calculate totals including subtotal, tax, shipping, and discounts. Add shipping address form with validation. Implement…