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/mark393295827/graph-engineering-architectures/agent-teams-commandnpx skills add Mark393295827/graph-engineering-architectures --skill agent-teams-commandgit clone --depth 1 https://github.com/Mark393295827/graph-engineering-architecturesWrote 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/mark393295827/graph-engineering-architectures/agent-teams-command)<a href="https://agentmods.dev/skills/mark393295827/graph-engineering-architectures/agent-teams-command"><img src="https://agentmods.dev/badge/skills/mark393295827/graph-engineering-architectures/agent-teams-command.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.01521 |
| Opus 5 | $0.00015 | $0.00760 |
| Sonnet 5 | $0.00006 | $0.00304 |
| Haiku 4.5 | $0.00003 | $0.00152 |
Grade A, and why
agent-teams-command 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 5d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Teams Command
<skill_contract> A mission with independently ownable workstreams, interfaces, permissions, budgets, and an integration owner. An isolated worker program, typed IPC ledger, serial integration, cleanup, and evidence receipts. Integrated artifacts pass mission checks and ownership, review, rollback, and cleanup gates. <non_goals>Graph-schema design, parallelism without net value, overlapping writers, or worker self-certification.</non_goals>
Strategic intent and final integration remain serial; owned execution may run
in parallel. graph-engineering may define dependency topology, but this skill
owns worker processes, exclusive territories, typed IPC, integration, and
cleanup. A Graph node is not automatically a teammate. Use the Ender lens for
commander understanding, Palantir for operational objects/actions, and von
Neumann for executable, inspectable process architecture. Detailed patterns:
references/ender-palantir-command-patterns.md; examples:
references/classic-campaigns.md.
Usage Template
Provide: mission, non-goals, workstreams, dependencies, files/systems, acceptance criteria, permissions, review bandwidth, runtime capabilities, budget, and integration owner.
Workflow
Admit a team only when at least two workstreams can proceed with low coordination, or distinct roles materially improve evaluation/safety. Calculate orchestration tax: setup, context duplication, IPC, merge conflict, review, and cleanup. If one process can finish within the same review budget, keep one process.
If dependencies and joins are the only complexity, use graph-engineering
without recruiting a team. Add workers only for nodes that need isolated
context, distinct ownership, or independent judgment.
<unknowns_gate>
Resolve commander intent, object/state vocabulary, ownership, dependency direction, verifier, join gate, and permission boundary before recruiting. Return NEEDS_INPUT when an irreversible business decision or authority cannot be discovered locally. Workers may probe implementation unknowns only inside their territory.
What ships with it
2 files 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.
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.
- 5d ago First seen · 124 lines · 30 tokens per session scan A 49b134c75cd1
agent-teams-command is a skill published in the GitHub repository Mark393295827/graph-engineering-architectures (2 stars, last pushed 15d ago), licensed MIT. It adds 30 tokens to every session and 1,521 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
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
python-package-management
Guide for managing packages in the Agent Framework Python monorepo, including creating new connector packages, versioning, and the lazy-loading pattern. Use this when adding, modifying, or releasing packages.
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.
verify-samples-tool
How to use the verify-samples tool to run, verify, and manage sample definitions in the Agent Framework repository. Use this when adding, updating, or running sample verification.
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-testing
Guidelines for writing and running tests in the Agent Framework Python codebase. Use this when creating, modifying, or running tests.