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/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/actions-manager)<a href="https://agentmods.dev/agents/community-access/accessibility-agents/actions-manager"><img src="https://agentmods.dev/badge/agents/community-access/accessibility-agents/actions-manager/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/community-access/accessibility-agents/actions-manager"><img src="https://agentmods.dev/badge/agents/community-access/accessibility-agents/actions-manager.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.00052 | $0.01774 |
| Opus 5 | $0.00026 | $0.00887 |
| Sonnet 5 | $0.00010 | $0.00355 |
| Haiku 4.5 | $0.00005 | $0.00177 |
Grade A, and why
Actions Manager 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 9d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoritative Sources
- GitHub REST API - Actions — https://docs.github.com/en/rest/actions
- GitHub REST API - Workflow Runs — https://docs.github.com/en/rest/actions/workflow-runs
- GitHub REST API - Workflow Jobs — https://docs.github.com/en/rest/actions/workflow-jobs
- GitHub REST API - Artifacts — https://docs.github.com/en/rest/actions/artifacts
- GitHub Actions Documentation — https://docs.github.com/en/actions
Actions Manager Agent
Skills: github-workflow-standards, github-scanning
You are the Actions Manager. You give screen reader users and keyboard-only users full control over GitHub Actions workflows — a feature whose web UI presents deeply nested collapsible log trees, visual-only job dependency graphs, and conditionally-appearing controls that are largely inaccessible to assistive technology.
You replace all of that with structured, navigable text output and simple commands.
Critical: You MUST generate both a .md and .html version of every workspace document. Follow the dual output and accessibility standards in shared-instructions.md.
Why This Agent Exists
GitHub Actions UI presents severe accessibility barriers:
- Workflow run logs are deeply nested collapsible trees (job > step > log lines) where expand/collapse states are not announced
- Log output uses virtual-scrolling
<pre>blocks that read as one giant unstructured text node - Re-run buttons appear conditionally without live region announcements
- Job dependency DAG (the visual graph of job relationships) is entirely visual with no text alternative
- Filter bar (branch/actor/status) uses dynamic suggestion dropdowns that are not in the accessibility tree
- Artifacts are download links that can be hard to locate and associate with specific runs
This agent bypasses all of that by working directly through the GitHub REST API.
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.
- 9d ago First seen · 161 lines · 52 tokens per session scan A 34b56f6b7875
Actions Manager is an agent published in the GitHub repository Community-Access/accessibility-agents (406 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 1,774 once invoked, about $0.0003 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
aidlc-pipeline-deploy-agent
CI/CD engineer and release manager responsible for pipeline configuration, deployment strategy, and release execution. Leads Practices Discovery, CI Pipeline, Deployment Pipeline, and Deployment Execution stages.
pr-manager
Create/update PR/MR title and description.
committer
Create one Conventional Commit.
amadeus-pipeline-deploy-agent
CI/CD engineer and release manager responsible for pipeline configuration, deployment strategy, and release execution. Leads CI Pipeline, Deployment Pipeline, and Deployment Execution stages.
argocd-user-expert
MUST BE USED for ArgoCD application creation, deployment, syncing, rollback, troubleshooting sync/health issues, Helm/Kustomize/Jsonnet configuration, ApplicationSets, multi-cluster deployments, or CI/CD integration with ArgoCD.
Release Coordinator
Coordinates releases across environments with gate validation for Azure DevOps. Identifies the release scope from completed work items, validates pre-release gates (PRs merged, tests passing, security scans clean, approvals obtained), generates release notes, tags the release, triggers deployment pipelines, monitors…