Borrowing it
Nothing to install: this file belongs to abuango/pos-ai. 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/abuango/pos-ai/main/.claude/skills/team-management/SKILL.mdgit clone --depth 1 https://github.com/abuango/pos-aiWrote 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/abuango/pos-ai/team-management)<a href="https://agentmods.dev/skills/abuango/pos-ai/team-management"><img src="https://agentmods.dev/badge/skills/abuango/pos-ai/team-management/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/abuango/pos-ai/team-management"><img src="https://agentmods.dev/badge/skills/abuango/pos-ai/team-management.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.00045 | $0.00773 |
| Opus 5.5 | $0.00018 | $0.00309 |
| Sonnet 5.5 | $0.00009 | $0.00155 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
team-management 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 2mo 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Management Skill
Setup
Before starting: check .handoff/sessions/ for active sessions, read context status.yaml, run git status. Follow .rules/universal.md (Plan -> Approve -> Execute).
Manage teams in the POS. Teams are organizational units led by TPMs.
Commands
/team create {name}- Create a new team with full setup/team list- List all teams/team status {name}- Show team status/team add-engineer {team} {specialty}- Add engineer to team
/team create {name} - Full Setup
Required Information: Team name (kebab-case), description, focus areas, tech stack, port range, engineer specialties.
Steps
-
Create directory structure
mkdir -p {teams_dir}/{team-name}/{repos,plans/sprints,logs,projects,docs} -
Create team.yaml at
{teams_dir}/{team}/team.yaml:name: "{team-name}" tpm: tpm-{team-name} description: "{description}" client: name: "{Client or Internal}" type: internal_product focus_areas: [...] tech_stack: backend: {framework} frontend: {framework} database: {db} engineers: [eng-backend, eng-frontend, eng-testing, eng-devops] active_projects: [] ports: range: "8X00-8X99 (backend), 3X00-3X99 (frontend)" created: "{today}" -
Create status.yaml at
{teams_dir}/{team}/status.yamlwithsession_active: false, empty task/blockers/sprints. -
Create QUICK-START.md with team name, TPM, focus, quick commands, key file paths, tech stack.
-
Add to platform registry - Edit
pos.yamlwith team entry underteams:. -
Create TPM agent at
.ai/agents/tpm-{team-name}.mdwith responsibilities (planning, coordination, quality, communication), available engineers, and workflow (receive assignment, create plan, execute after approval, report). -
Run agent linking:
./scripts/link-team-agents.shRestart Claude Code after linking.
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.
- 2mo ago First seen · 92 lines · 45 tokens per session scan A 6f9860906e86
team-management is a skill published in the GitHub repository abuango/pos-ai (2 stars, last pushed 7mo ago), licensed MIT. It adds 45 tokens to every session and 773 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.