Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add andreymudri/claude-teammates/plugin install claude-teammatesWrote 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/andreymudri/claude-teammates/executing-plans)<a href="https://agentmods.dev/skills/andreymudri/claude-teammates/executing-plans"><img src="https://agentmods.dev/badge/skills/andreymudri/claude-teammates/executing-plans.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.00030 | $0.00746 |
| Opus 5 | $0.00015 | $0.00373 |
| Sonnet 5 | $0.00006 | $0.00149 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
executing-plans 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executing Plans
Adapted from the MIT-licensed superpowers plugin by Jesse Vincent. See NOTICE.md.
Execute a written plan inline, in this session, task by task, checkpointing with your human
partner as you go. This is the counterpart to parallel-execution: same run state, different
cadence. Use using-teammates to decide which one applies before reaching for this skill.
1. Initialize the run
node "$CLAUDE_PLUGIN_ROOT/scripts/cli.mjs" init-run <planPath> --run <runId> --root <project root>
This writes .teammates/<runId>/plan.json and status.json — the same shared state a fleet
run would write. Because of that:
node "$CLAUDE_PLUGIN_ROOT/scripts/cli.mjs" digest --run <runId> --root <project root>renders this run unchanged, whether it ran inline or across teammates.fleet-lifecycle resume <runId>can resume it later.- If the work turns out to be bigger than expected mid-run, hand it to
parallel-executionwithout translating anything — the state is already in the shape it expects.
Never start implementation on main/master without explicit consent from your human partner.
2. Review the plan critically
Read it fully before touching code. Raise concerns with your human partner before starting — gaps, unclear steps, or a task that looks bigger than a single sitting.
3. Execute and checkpoint
Work through tasks in dependency order. Follow each step; run the verifications it specifies.
Checkpoint with your human partner per task, or per small batch of related tasks — not automatically per phase the way a fleet gate does, and not silently at the end of the whole plan. Report what changed, what you verified, and any deviation from the plan before moving on.
Gate manifest is optional here
A fleet phase demands a teammates.gate.json manifest before it will pass. Inline work does
not need one. When no manifest exists, checkpoint against the plan's own verification steps
instead of demanding one be written first.
Do not require a phase structure, a manifest, or a reviewer dispatch for small inline work.
Ceremony that makes a two-task change expensive is ceremony that gets skipped — and a skipped
skill protects nothing. Reserve that machinery for work that has actually grown into a fleet
(see parallel-execution and phase-gate).
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 · 71 lines · 30 tokens per session scan A 08c3b3e73cde
executing-plans is a skill published in the GitHub repository andreymudri/claude-teammates (2 stars, last pushed 4d ago), licensed MIT. It adds 30 tokens to every session and 746 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.
Other skills, from other repositories
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
python-development
Coding standards, conventions, and patterns for developing Python code in the Agent Framework repository. Use this when writing or modifying Python source files in the python/ directory.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…