pos-ai: Skill for Claude Code

.claude/skills/team-management/SKILL.md

team-management is a skill for Claude Code from abuango/pos-ai. It costs 45 tokens per session (773 once invoked), scanned A, original, MIT.

A skill for creating and managing engineering teams in a POS, or project operating system. Teams are organisational groups led by technical project managers, with members, projects, documentation, and configuration.

In plain words
What is it for?
Use it to create a team, list or check teams, or add engineers with particular specialties.
Why use it?
It gives team setup a defined process instead of leaving directories, team details, and memberships inconsistent. It also checks active handoff sessions and project status before changes.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions Claude Code.

This is abuango/pos-ai's own configuration. It tells Claude Code how to work on pos-ai itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything pos-ai configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is ./scripts/link-team-agents.sh.

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/abuango/pos-ai/main/.claude/skills/team-management/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/abuango/pos-ai

Made for: Claude Code.

Wrote 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.

agentmods badge for team-management

README.md
[![agentmods](https://agentmods.dev/badge/skills/abuango/pos-ai/team-management/github.svg)](https://agentmods.dev/skills/abuango/pos-ai/team-management)
Your own site
<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.

agentmods 80×15 button for team-management

Your own site · 80×15
<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>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 773 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.00773
Opus 5 $0.00023 $0.00387
Sonnet 5 $0.00009 $0.00155
Haiku 4.5 $0.00005 $0.00077

Measured 9d ago against content hash 6f9860906e86, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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 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.

.claude/skills/team-management/SKILL.md · 92 lines

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

  1. Create directory structure

    mkdir -p {teams_dir}/{team-name}/{repos,plans/sprints,logs,projects,docs}
    
  2. 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}"
    
  3. Create status.yaml at {teams_dir}/{team}/status.yaml with session_active: false, empty task/blockers/sprints.

  4. Create QUICK-START.md with team name, TPM, focus, quick commands, key file paths, tech stack.

  5. Add to platform registry - Edit pos.yaml with team entry under teams:.

  6. Create TPM agent at .ai/agents/tpm-{team-name}.md with responsibilities (planning, coordination, quality, communication), available engineers, and workflow (receive assignment, create plan, execute after approval, report).

  7. Run agent linking:

    ./scripts/link-team-agents.sh
    

    Restart Claude Code after linking.

Read the full file on GitHub · 92 lines

Files

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.

Changes

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.

  1. 9d ago First seen · 92 lines · 45 tokens per session scan A 6f9860906e86

Subscribe to this mod's changes

team-management is a skill published in the GitHub repository abuango/pos-ai (2 stars, last pushed 5mo ago), licensed MIT. It adds 45 tokens to every session and 773 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-08-31.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

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…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens