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.
npx agentmods add skills/requix/kiro-team/plan-with-teamnpx skills add requix/kiro-team --skill plan-with-teamgit clone --depth 1 https://github.com/requix/kiro-teamWrote 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/requix/kiro-team/plan-with-team)<a href="https://agentmods.dev/skills/requix/kiro-team/plan-with-team"><img src="https://agentmods.dev/badge/skills/requix/kiro-team/plan-with-team.svg" alt="Measured on agentmods" 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.00049 | $0.00806 |
| Opus 5 | $0.00024 | $0.00403 |
| Sonnet 5 | $0.00010 | $0.00161 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade A, and why
plan-with-team 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 6d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions: Plan With Team
You are receiving these instructions because the user invoked @plan-with-team. The user's message that triggered this skill IS their task description. Everything the user wrote is what you need to plan. Do NOT ask for clarification — plan it now.
What To Do
- Take the user's message as the task to plan
- Create a spec file at
specs/<kebab-case-name>.md - Use the format below
- Report what you created
Rules
- NEVER ask "What would you like to build?" — the user already told you
- PLANNING ONLY — do NOT write code or deploy agents
- Generate a kebab-case filename from the task (e.g.,
azure-blob-storage-module) - Do NOT prepend
issue-,adw-, or any prefix to the filename - Explore the codebase first to understand existing patterns
Spec Format
# Plan: <task name>
## Task Description
<describe the task in detail>
## Objective
<clearly state what will be accomplished>
## Problem Statement
<define the specific problem or opportunity>
## Solution Approach
<describe the proposed solution>
## Relevant Files
<list files relevant to the task>
### New Files
<list new files to be created>
## Team Orchestration
> **Worktree Isolation**: The team-lead creates an isolated git worktree for this spec using `scripts/worktree-create.sh`. All builders work inside this worktree. After final validation, changes are merged back via `scripts/worktree-merge.sh`.
### Team Members
- **Builder**
- Name: <unique name>
- Role: <specific focus>
- Agent: builder
- **Validator**
- Name: <unique name>
- Role: Verify implementation meets criteria
- Agent: validator
- **Documenter**
- Name: <unique name>
- Role: Generate documentation
- Agent: documenter
## Step by Step Tasks
### 1. <Task Name>
- **Task ID**: <kebab-case-id>
- **Depends On**: none
- **Assigned To**: <team member>
- **Agent**: builder
- **Actions**:
- <action>
- **Acceptance Criteria**:
- <criterion>
### N-1. Final Validation
- **Task ID**: validate-all
- **Depends On**: <all previous>
- **Assigned To**: validator
- **Agent**: validator
- **Checks**:
- Run all validation commands
- Verify acceptance criteria met
### N. Documentation
- **Task ID**: generate-docs
- **Depends On**: validate-all
- **Assigned To**: documenter
- **Agent**: documenter
- **Actions**:
- Generate documentation in `app_docs/`
## Acceptance Criteria
<measurable criteria>
## Validation Commands
<commands to verify>
## Notes
<optional context>
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.
- 6d ago First seen · 133 lines · 49 tokens per session scan A 4bf007440441
plan-with-team is a skill published in the GitHub repository requix/kiro-team (38 stars, last pushed 4mo ago), licensed MIT. It adds 49 tokens to every session and 806 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-30.
Other skills, from other repositories
takt
TAKT ワークフローエンジン。codex exec でサブエージェントを起動し、ワークフロー YAML（steps / initialstep）に従って マルチエージェントオーケストレーションを実行する。.
takt
TAKT ワークフローエンジン。Agent Team を使ったマルチエージェントオーケストレーション。ワークフロー YAML（steps / initialstep）に従ってマルチエージェントを実行する。.
company-product-context
Compiles comprehensive company product context from PDF documents, web research, and industry knowledge.
codebase-context-extractor
This skill provides a comprehensive context extraction system for large codebases. It intelligently analyzes code structure, dependencies, and relationships to extract relevant context for understanding, debugging, or modifying code.
skill-creator
Generates Anthropic Skills with complete workflow including GitHub PR creation and local download verification.
Research Synthesis Workflow
A step-by-step guide to synthesizing research from multiple sources into a coherent summary.