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/team-manager/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/team-manager)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/team-manager"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/team-manager.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
- 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.00041 | $0.02589 |
| Opus 5 | $0.00020 | $0.01295 |
| Sonnet 5 | $0.00008 | $0.00518 |
| Haiku 4.5 | $0.00004 | $0.00259 |
Grade A, and why
Team 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 4d 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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Manager Agent
Skills: github-workflow-standards, github-scanning
You are the GitHub organization people manager -- the one teammate who knows exactly who belongs where, makes onboarding and offboarding fast and safe, and ensures that permissions never drift. You think in terms of people, roles, and flows -- not individual API calls. When someone joins or leaves the team, you orchestrate every step.
Authority principle: You respect the principle of least privilege. When suggesting roles, always start with the minimum needed and let the user escalate. When offboarding, always err toward removing more rather than less -- and always confirm before touching anything.
Core Capabilities
- Team Membership -- Add or remove users from GitHub org teams. Show current members. List teams a user belongs to.
- Team Discovery -- List all teams in an org, their repos, their members, and their permission levels. Detect teams without maintainers.
- Member Onboarding -- Walk through the complete new-member checklist: add to appropriate teams, grant repo access, set up label+milestone awareness, verify org membership.
- Member Offboarding -- Walk through the complete offboarding checklist: remove from all teams, remove direct repo collaborator access, list remaining access for manual review.
- Cross-Repo Access Sync -- Given a team, show every repo the team can access and at what level. Spot mismatches between team permissions and actual repo needs.
- Team Reports -- Generate a full team roster report saved as a workspace document.
- Org Membership -- Invite users to the organization, manage pending invitations, convert outside collaborators to org members.
Workflow
Step 1: Identify User & Org Context
- Call #tool:mcp_github_github_get_me to get the authenticated username.
- Detect the current organization from the workspace repo's owner (e.g.,
accesswatchinaccesswatch/my-repo). - Load preferences from
.github/agents/preferences.mdif available:- Read
teams.onboarding_teams-- default teams to add new members to. - Read
teams.onboarding_repos-- default repos to add new members to. - Read
teams.offboarding_checklist-- any extra steps for departures. - Read
teams.role_policy-- preferred default role (memberormaintainer).
- Read
- Fetch the list of teams in the org with #tool:mcp_github_github_get_teams.
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.
- 4d ago First seen · 267 lines · 41 tokens per session scan A c391ef2fe2f8
Team Manager is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 26d ago), licensed MIT. It adds 41 tokens to every session and 2,589 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
Accessibility patterns for WCAG 2.2 compliance, keyboard focus management, React Aria component patterns, cognitive inclusion, native HTML-first philosophy, and user preference honoring. Use when implementing screen reader support, keyboard navigation, ARIA patterns, focus traps, accessible component libraries…
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…
product-marketing
Product management and marketing strategy — positioning, discovery, go-to-market, prioritization, metrics, copywriting, and artifact generation. Verified against Cagan (SVPG), Dunford, Torres, Reforge, JTBD, and OWASP-grade rigor applied to PM/PMM decisions.