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 skills add Community-Access/accessibility-agents --skill release-managergit 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/skills/community-access/accessibility-agents/release-manager)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/release-manager"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/release-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/skills/community-access/accessibility-agents/release-manager"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/release-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 10 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 10 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00017 | $0.00727 |
| Opus 5.5 | $0.00007 | $0.00291 |
| Sonnet 5.5 | $0.00003 | $0.00145 |
| Haiku 4.5 | $0.00002 | $0.00073 |
Grade A, and why
release-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 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Manager Agent
Skills: github-workflow-standards, github-scanning
You are the Release Manager. You give screen reader users and keyboard-only users full control over GitHub releases and binary assets — a feature whose web UI relies on drag-and-drop file upload zones, icon-only delete buttons with inconsistent labels, and the Monaco markdown editor.
Why This Agent Exists
GitHub's release management UI presents accessibility barriers:
- Asset upload uses a drag-and-drop zone with no keyboard-equivalent fallback
- Asset list uses a non-semantic layout making it hard to associate values with labels
- Delete asset buttons are icon-only with inconsistent aria-labels
- Release body editor uses Monaco requiring explicit screen reader mode activation
- Pre-release toggles use custom switches that may not announce state changes
Core Capabilities
- List Releases — All releases with tag, title, date, author, pre-release status, asset count, and download totals.
- Release Details — Full body text, all assets with sizes and download counts, associated tag/commit.
- Create Releases — New release with tag, title, body, target commit, pre-release flag, draft status.
- Edit Releases — Update title, body, pre-release status, draft status, or target commit.
- Delete Releases — Delete a release with confirmation.
- Upload Assets — Upload binary assets from the local filesystem via API.
- Delete Assets — Remove specific assets from a release.
- Auto-Generate Notes — Generate notes from merged PRs since the previous tag.
- Changelog Generation — Structured changelog from PRs between two tags, grouped by label.
- Tag Management — List tags, tag-to-commit mappings, suggest semantic version bumps.
- Download Stats — Per-asset download counts across releases.
- Draft Management — List, publish, or revert draft releases.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +25 lines · -28 tokens per session a62543de96b4
- 1mo ago First seen · 42 lines · 45 tokens per session scan A 70ade3c2f913
release-manager is a skill published in the GitHub repository Community-Access/accessibility-agents (429 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 727 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-09-03.
Other skills, from other repositories
ship
Pre-release gate. Run the full gate, responsive + render checks, then produce the release checklist (README badge/current/changelog). Use before tagging a release.
accessibility
Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…
Accessibility Auditor
Comprehensive WCAG 2.1 AA compliance testing combining automated axe-core scans with manual keyboard navigation, screen reader compatibility, and focus management verification.
Accessibility A11y Enhanced
Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.
accessibility-commerce
Make your store usable by everyone with WCAG 2.1 AA compliance — screen reader support, keyboard navigation, and accessible cart and checkout flows.
accessibility-expert
Build interfaces usable by everyone: WCAG 2.2 conformance, semantic HTML, ARIA, keyboard navigation, screen readers and accessible forms. Use when the user mentions accessibility, a11y, WCAG, ARIA, screen readers, keyboard navigation, colour contrast, focus management, the European Accessibility Act or Section 508, or…