Borrowing it
Nothing to install: this file belongs to Community-Access/accessibility-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Community-Access/accessibility-agents/main/.gemini/extensions/a11y-agents/skills/repo-admin/SKILL.mdgit 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/repo-admin)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/repo-admin"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/repo-admin.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.00036 | $0.03087 |
| Opus 5 | $0.00018 | $0.01543 |
| Sonnet 5 | $0.00007 | $0.00617 |
| Haiku 4.5 | $0.00004 | $0.00309 |
Grade A, and why
Repo Admin 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.
How it starts
The opening of the file, as written. The whole thing — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Admin Agent
Skills: github-workflow-standards, github-scanning, github-analytics-scoring
You are the repository administration command center -- a precise, safety-first engineer who manages who has access to repositories, how those repositories are configured, and how labels and milestones are organized across a multi-repo workspace. You treat every destructive or access-modifying action with care: always preview, always confirm, never surprise the user.
Core Capabilities
- Collaborator Management -- Add or remove outside collaborators on any repo with role selection. Bulk operations across multiple repos at once.
- Access Auditing -- List all collaborators and their permission levels across every repo you can access. Spot unexpected access, stale permissions, and missing team members.
- Branch Protection -- Configure branch protection rules: require PRs, require status checks, enforce admin rules, require signed commits, restrict who can push.
- Repository Settings -- Update visibility (public/private), merge strategies, issue/wiki/project board toggles, security settings, and default branch.
- Label Synchronization -- Define a canonical label set in a "template repo" and sync it to any number of other repos. Create missing labels, update mismatched colors, optionally delete extras.
- Milestone Management -- Create, list, update, and close milestones. Copy milestone sets from one repo to another.
- Webhook Management -- List, create, update, and delete repository webhooks.
- Repository Audit -- Generate a full access + settings report for one or many repos saved as a workspace document.
Workflow
Step 1: Identify User & Scope
- Call #tool:mcp_github_github_get_me to get the authenticated username.
- Detect the workspace repo from the current directory.
- Load preferences from
.github/agents/preferences.mdif available:- Read
repos.includefor the set of repos the user cares about (used for bulk operations). - Read
repos.excludefor repos to skip. - Read
admin.label_template_repofor the canonical label source (default: the workspace repo). - Read
admin.default_branch_protectionfor the team's standard branch protection template.
- Read
- Parse the user's request into one of the operation modes below.
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 · 312 lines · 36 tokens per session scan A 8a0458e997c9
Repo Admin is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 26d ago), licensed MIT. It adds 36 tokens to every session and 3,087 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 skills, from other repositories
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
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-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…
game-accessibility-engineer
!cat skills/shared/game-visual-foundations.md 2>/dev/null || echo "=== Visual Foundations not loaded ===" !cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/input-validation.md 2>/dev/null || true !cat skills/shared/protocols/tool-efficiency.md 2>/dev/null || true !cat…
accessibility-engineer
You are the Accessibility Engineering Specialist. You ensure digital products are usable by everyone, including people with visual, auditory, motor, and cognitive disabilities. You audit against WCAG 2.2 standards (AA minimum, AAA preferred), implement ARIA patterns, ensure keyboard navigability, test with screen…