A sprint command that assigns approved work to several coordinated coding agents at the same time. A sprint is a planned set of tasks completed within a defined work period.

Use it to validate an approved sprint plan, create an agent team, and run parallel tasks for that team.

It reduces waiting when a sprint contains at least two tasks that can be done independently, while checking the project's required plans and status first.

How abuango/pos-ai configures Claude Code

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

README.md

[![agentmods](https://agentmods.dev/badge/skills/abuango/pos-ai/team-sprint/github.svg)](https://agentmods.dev/skills/abuango/pos-ai/team-sprint)

Your own site

<a href="https://agentmods.dev/skills/abuango/pos-ai/team-sprint"><img src="https://agentmods.dev/badge/skills/abuango/pos-ai/team-sprint/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/abuango/pos-ai/team-sprint"><img src="https://agentmods.dev/badge/skills/abuango/pos-ai/team-sprint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,480 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.

Model	Per session	Once invoked
Fable 5.1	$0.00046	$0.01480
Opus 5	$0.00023	$0.00740
Sonnet 5	$0.00009	$0.00296
Haiku 4.5	$0.00005	$0.00148

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

Security

Grade A, and why

team-sprint 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 8d 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-sprint/SKILL.md · 137 lines

How it starts

The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Team Sprint Execution

Setup

Before starting: check .handoff/sessions/ for active sessions, read context status.yaml, run git status. Follow .rules/universal.md (Plan -> Approve -> Execute).

Execute an approved sprint plan using Claude Code Agent Teams for parallel task execution.

Usage

/team-sprint {team}

Arguments:

{team} — Team name (required). Must have an approved sprint plan.

Prerequisites

Approved sprint plan exists in teams/{team}/plans/sprints/
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 is set (configured in .claude/settings.json)
Sprint has 2+ parallelizable tasks (otherwise use standard handoff workflow)

Process

Phase 1: Load & Validate Sprint

Read team status from contexts/{context}/status.yaml
Find the current/target sprint plan in contexts/{context}/plans/sprints/
Validate sprint is approved (check approved_sprints in status.yaml)
Parse sprint tasks, identify parallelizable work items
If fewer than 2 parallelizable tasks, recommend standard handoff workflow instead

Phase 2: Create Team

TeamCreate with name {team}-sprint-{n} (e.g., my-project-sprint-5)
Determine teammate count from sprint task assignments (one per unique engineer role, max 4)
Spawn teammates via Task tool with:
- team_name: the team name from TeamCreate
- name: descriptive role name (e.g., backend-engineer, frontend-engineer)
- subagent_type: general-purpose
- mode: default (NOT plan — plan mode causes cycling where agents re-enter plan mode after every tool use, requiring 10+ approvals per task)
- Context prompt MUST include:
  - Team name and repo path
  - Sprint plan reference
  - Their assigned tasks
  - Working directory and branch to use
  - Reminder to commit after each task
  - MANDATORY: "Before your FIRST implementation, you MUST use EnterPlanMode, outline your plan, then ExitPlanMode to get approval from the team lead. After your plan is approved, implement freely without re-entering plan mode. Do NOT implement without initial plan approval."

Read the full file on GitHub · 137 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.

SKILL.md.tmpl 5.6 KB

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.

8d ago First seen · 137 lines · 46 tokens per session scan A 3e87514e6fad

Subscribe to this mod's changes

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

Building agents Planning

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

pos-ai: Skill for Claude Code