agentmods.dev

team-structure

team-structure is a skill for Claude Code, Codex from bostonaholic/team. It costs 33 tokens per session (859 once invoked), scanned A, original, MIT.

A planning method that divides a reviewed software design into vertical slices, with a verification checkpoint for each slice. A vertical slice delivers a complete piece of behavior across the parts it touches.

In plain words
What is it for?
Use it to break an approved design into implementation steps and checkpoints before coding begins.
Why use it?
Large designs can be difficult to implement and check as one task. This creates smaller work units while keeping each unit tied to a way to verify it.

Skill for Claude CodeCodex

Written for Claude Code and Codex: argument-hint in frontmatter, but also agents/openai.yaml present. Also seen: names the AskUserQuestion tool.

Part of the team plugin — 88 skills, 13 agents, 2 hooks shipped together

not rated 11repo changed yesterday A scan 33 tokens original MIT

Good fit Use it to break an approved design into implementation steps and checkpoints…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bostonaholic/team/team-structure
View source ↗ bostonaholic/team team.bostonaholic.dev
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add bostonaholic/team --skill team-structure
Clone the repo
git clone --depth 1 https://github.com/bostonaholic/team

Made for: Claude Code, Codex.

Or install team, the plugin that ships this one along with the rest of its 88 skills, 13 agents, 2 hooks.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/bostonaholic/team/team-structure.svg)](https://agentmods.dev/skills/bostonaholic/team/team-structure)
Your own site
<a href="https://agentmods.dev/skills/bostonaholic/team/team-structure"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/team-structure.svg" alt="Measured on agentmods" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 859 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.00033 $0.00859
Opus 5 $0.00016 $0.00430
Sonnet 5 $0.00007 $0.00172
Haiku 4.5 $0.00003 $0.00086

Measured yesterday against content hash 570da808ab9c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

team-structure 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 yesterday.

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.

skills/team-structure/SKILL.md · 72 lines

How it starts

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

Team Structure — How Do We Get There?

Run the STRUCTURE phase. It runs autonomously and advances to PLAN — there is no gate here. Nothing is presented for approval mid-run.

Input

$ARGUMENTS is the artifact directory: docs/plans/<id>/. If empty, the discovery command below resolves it.

The structure-planner reads:

  • $ARGUMENTS/6-design.md (the reviewed design — the latest $ARGUMENTS/design-review-<n>.md must carry a passing verdict)
  • $ARGUMENTS/5-research.md
  • $ARGUMENTS/1-task.md (for cross-reference, not for re-litigating intent)

Resolve <team-skill-dir> to the absolute directory containing skills/team/SKILL.md. From the repository root, run the command below. Its predecessor filter requires a 6-design.md whose latest design-review-<n>.md carries a passing verdict (APPROVE or COMMENT), so unreviewed or REQUEST-CHANGES candidates are skipped:

"<team-skill-dir>/discover-topic.sh" "${ARGUMENTS:-}" "6-design.md" --require-passing-review
  • If the command printed a path, use it as $ARGUMENTS for the rest of this skill (tier 1 explicit arg, or tier 2 discovery of a reviewed predecessor). When the path came from tier 2 (no explicit arg), announce the resolved directory to the user before proceeding, so an auto-picked topic is never silent.
  • If the command printed nothing (tier 3 — no directory holds a 6-design.md with a passing design review), do not hard-error. Fire AskUserQuestion with a Setup header and labeled options:
    • Run the producer — run /team-design docs/plans/<id>/ to produce and review 6-design.md.
    • Give a path — the user supplies the docs/plans/<id>/ directory directly (run ls docs/plans/ to find your topic directory).

Execution

  1. Use the directory resolved in ## Input, then verify the review gate: the highest-<n> $ARGUMENTS/design-review-<n>.md must carry verdict: APPROVE or verdict: COMMENT in its YAML frontmatter (the tier-2 filter already enforced this. Re-check a tier-1 explicit path). If no review artifact exists, or the latest verdict is REQUEST CHANGES, refuse: report that the design has not passed review and suggest /team-design $ARGUMENTS — never slice an unreviewed design. No recorded verdict counts as not passed (principle-fail-closed).
  2. Dispatch structure-planner, which writes $ARGUMENTS/7-structure.md with vertical slices. The artifact carries plain frontmatter (topic, date, phase: structure) — no approval fields, because structure is not gated.
  3. No gate. Nothing is presented for approval mid-run. Within a full /team run the orchestrator advances to PLAN automatically. Run standalone, this skill stops after writing the structure and reports the next command.
  4. Stop once $ARGUMENTS/7-structure.md exists.

Read the full file on GitHub · 72 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. yesterday Changed · -47 lines · -14 tokens per session 570da808ab9c
  2. 3d ago First seen · 119 lines · 47 tokens per session scan A 3e6881c1c227

Subscribe to this mod's changes

team-structure is a skill published in the GitHub repository bostonaholic/team (11 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 859 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.

Claude CodePlanningProject managementagent-orchestrationagent-skillsagentic-aiagentic-workflow
Related

Other skills, from other repositories

gsd-tools

Central utility skill for GSD operations. Provides config parsing, slug generation, timestamps, path operations, and orchestrates calls to other specialized skills. Acts as the unified entry point that the original gsd-tools.cjs provided via its lib/ modules (commands, config, core, init).

a5c-ai/babysitter · 62 tokens

babysit-babysitter-issues

This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.

a5c-ai/babysitter · 69 tokens

spec-driven-development

Specification creation and management for the Pilot Shell methodology. Covers semantic search, clarifying questions, structured spec generation, and iterative refinement.

a5c-ai/babysitter · 30 tokens

cog-meeting-processing

Process meeting recordings and transcripts into decisions, action items, and team dynamics.

a5c-ai/babysitter · 20 tokens

cog-onboarding

Personalize COG Second Brain workflow through role pack selection and vault initialization.

a5c-ai/babysitter · 19 tokens

cog-team-intelligence

Cross-reference GitHub, Linear, Slack, and PostHog with bidirectional sync for team briefs.

a5c-ai/babysitter · 26 tokens