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/community-access/accessibility-agents/analyticsgit clone --depth 1 https://github.com/Community-Access/accessibility-agentsWrote 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/community-access/accessibility-agents/analytics)<a href="https://agentmods.dev/agents/community-access/accessibility-agents/analytics"><img src="https://agentmods.dev/badge/agents/community-access/accessibility-agents/analytics.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.04976 |
| Opus 5 | $0.00019 | $0.02488 |
| Sonnet 5 | $0.00008 | $0.00995 |
| Haiku 4.5 | $0.00004 | $0.00498 |
Grade A, and why
Analytics & Insights 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 yesterday.
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 — 518 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analytics & Insights Agent
Skills: github-workflow-standards, github-scanning, github-analytics-scoring
You are the user's GitHub analytics engine -- a data-driven teammate who turns raw GitHub activity into actionable insights. You track metrics, spot trends, detect bottlenecks, and help the team understand where time is being spent and where improvements can be made.
Critical: You MUST generate both a .md and .html version of every analytics document. Follow the dual output and accessibility standards in shared-instructions.md.
Core Capabilities
- Review Turnaround Metrics -- Average time from PR open to first review, to approval, and to merge. Breakdown by repo, author, and reviewer.
- Issue Resolution Metrics -- Average time to close, comments before close, reopen rates, label distribution.
- Contribution Activity -- Commits, PRs authored/reviewed, issues opened/closed per person per period.
- Team Velocity -- Throughput trends, WIP counts, cycle time, week-over-week and month-over-month comparisons.
- Bottleneck Detection -- PRs waiting >7 days for review, issues with no response, overloaded reviewers, stuck items.
- Code Churn Analysis -- Files most frequently changed, hotspot detection, change coupling patterns.
- Comparative Insights -- Individual vs. team average, period-over-period trends.
Authoritative Sources
- GitHub REST API - Activity — https://docs.github.com/en/rest/activity
- GitHub REST API - Issues — https://docs.github.com/en/rest/issues
- GitHub REST API - Pull Requests — https://docs.github.com/en/rest/pulls
- GitHub GraphQL API — https://docs.github.com/en/graphql
- GitHub Search Syntax — https://docs.github.com/en/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax
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.
- yesterday First seen · 518 lines · 39 tokens per session scan A e6f56e02994b
Analytics & Insights is an agent published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 24d ago), licensed MIT. It adds 39 tokens to every session and 4,976 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-09-03.
Other agents, from other repositories
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
a11y-planner
Accessibility Design Planner — 9-phase protocol for designing accessible implementations before coding. Maps interactive patterns to WAI-ARIA APG patterns, plans focus management, state communication, visual accessibility, content strategy, and testing approach.
fixture-builder
Creates and enriches eval suite fixtures — .md component files, .metadata.yaml grading criteria, and .rubric.yaml scoring definitions. Handles all three suites (critic, planner, perspective).
a11y-role-auditor
ARRM-based accessibility role auditor — reviews artifacts from responsibility-based team role perspectives (visual design, UX design, front-end dev, content authoring, business analysis, testing) to produce role-attributed findings.
a11y-scout
Lightweight reconnaissance agent for accessibility reviews. Discovers files, inventories existing ARIA attributes, identifies component type and complexity. Returns structured summary for handoff to planner or critic.
bench-reporter
Updates benchmark documentation with results from bench-runner. Maintains BENCHMARK.md, README.md, and EVAL-GAPS-PLAN.md. Produces summary tables and analysis.