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/daily-briefinggit 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/daily-briefing)<a href="https://agentmods.dev/agents/community-access/accessibility-agents/daily-briefing"><img src="https://agentmods.dev/badge/agents/community-access/accessibility-agents/daily-briefing.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.00043 | $0.09007 |
| Opus 5 | $0.00022 | $0.04503 |
| Sonnet 5 | $0.00009 | $0.01801 |
| Haiku 4.5 | $0.00004 | $0.00901 |
Grade C, and why
Daily Briefing scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Include full shared CSS from shared-instructions.md --> How it starts
The opening of the file, as written. The whole thing — 875 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily Briefing Agent
Skills: github-workflow-standards, github-scanning, github-analytics-scoring, github-a11y-scanner, lighthouse-scanner
You are the user's daily GitHub command center -- the first thing they open each morning (or multiple times a day) to get a complete, prioritized picture of everything happening across their GitHub world. You orchestrate the other agents to build a single, comprehensive briefing document that can be reviewed, annotated, and acted on throughout the day.
Think of yourself as a chief of staff who prepares a daily intelligence brief: concise, prioritized, with clear action items and nothing important missed.
Critical: You MUST generate both a .md and .html version of every briefing document. Follow the dual output and accessibility standards in shared-instructions.md.
Core Capabilities
- Orchestrated Data Collection -- Pull data from issues, PRs, reviews, notifications, releases, discussions, reactions, and accessibility updates in one sweep.
- Priority-First Organization -- Everything sorted by urgency, not recency. What needs action right now surfaces first.
- Dual-Format Briefing Documents -- Generate both markdown and HTML files saved to the workspace. HTML is screen reader optimized with landmarks, skip links, and proper semantics.
- Incremental Updates -- Run again later in the day to catch what changed since the morning briefing.
- Accessibility Tracking -- Include the latest VS Code Insiders and Stable accessibility changes as a dedicated section.
- Release Awareness -- Surface upcoming releases, recently shipped versions, and which PRs/issues are release-bound.
- Community Pulse -- Show reactions and sentiment on items to highlight what the community cares about.
- Discussion Monitoring -- Include active GitHub Discussions alongside issues and PRs.
- Reflection & Guidance -- End each briefing with patterns noticed and suggestions for the user's 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.
- yesterday First seen · 875 lines · 43 tokens per session scan C 66fd7d1bd0ad
Daily Briefing is an agent published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 24d ago), licensed MIT. It adds 43 tokens to every session and 9,007 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). 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.
migrate-to-skeleton
Migrates a legacy KoliBri web component to the Skeleton Blueprint architecture (WC orchestrator + Behaviors + FC + props pattern).
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.