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/markus-global/markus/team-buildingnpx skills add markus-global/markus --skill team-buildinggit clone --depth 1 https://github.com/markus-global/markusWrote 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/markus-global/markus/team-building)<a href="https://agentmods.dev/skills/markus-global/markus/team-building"><img src="https://agentmods.dev/badge/skills/markus-global/markus/team-building.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 | $0.00018 | $0.05386 |
| Opus 5 | $0.00009 | $0.02693 |
| Sonnet 5 | $0.00004 | $0.01077 |
| Haiku 4.5 | $0.00002 | $0.00539 |
Grade A, and why
team-building 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 4d 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 — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Building
This skill teaches you how to create Markus team packages — self-contained directory-based artifacts that define a group of specialized AI agents with shared norms and coordination structure.
Core Philosophy
Every agent in a team must be a specialist. Do NOT simply pick generic templates and give them names. Design each agent with a unique identity, expertise, and detailed role documentation. Safety constraints are defined in each agent's POLICIES.md, not through tool restrictions.
Artifact Directory
CRITICAL: Team artifacts MUST be saved under this exact path — the Builder page, install system, and deliverable detection all depend on it:
~/.markus/builder-artifacts/teams/{team-name}/
├── team.json # Manifest (you write via file_write)
├── README.md # Public-facing team overview for Hub/Builder (REQUIRED)
├── ANNOUNCEMENT.md # Team announcement (you write via file_write)
├── NORMS.md # Working norms (you write via file_write)
├── images/ # Team-level images (icon, etc.)
│ └── icon.png # Team icon — used as avatar after install
├── workflows/ # Workflow templates (optional)
│ └── {workflow-name}.yaml # YAML workflow DAG definition
└── members/
├── {manager-slug}/
│ ├── ROLE.md # Identity and system prompt (REQUIRED)
│ ├── HEARTBEAT.md # Periodic self-check checklist (RECOMMENDED)
│ ├── POLICIES.md # Constraints and guardrails (optional)
│ ├── CONTEXT.md # Domain context and references (optional)
│ └── images/ # Member avatar images (e.g. avatar.jpg)
└── {worker-slug}/
├── ROLE.md # Identity and system prompt (REQUIRED)
├── HEARTBEAT.md # Periodic self-check checklist (RECOMMENDED)
├── POLICIES.md # Constraints and guardrails (optional)
├── CONTEXT.md # Domain context and references (optional)
└── images/ # Member avatar images (e.g. avatar.jpg)
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.
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.
- 4d ago First seen · 400 lines · 18 tokens per session scan A 613b1b0a8290
team-building is a skill published in the GitHub repository markus-global/markus (157 stars, last pushed 7d ago), licensed Apache-2.0. It adds 18 tokens to every session and 5,386 once invoked, about $0.0001 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
dashclaw-ship
The single command that gets a DashClaw change ON MAIN AND LIVE — it resolves everything blocking production, never defers, and never hands back a checklist. Lands feature branches on main (rebase, gate, merge, push so Vercel deploys), bumps the unified platform+SDK version, and realigns every description of the…
dashclaw-governance
Governance behavior for AI agents governed by DashClaw. Teaches the governance protocol: when to call guard (risk thresholds), how to interpret decisions (allow/warn/block/requireapproval), when to record actions, how to wait for approvals, and session lifecycle management. Loads org-specific policies and capabilities…
instrument-agent
Integrate DashClaw SDK into any agent using the 4-step governance loop.
troubleshoot
Debug DashClaw errors, signal issues, and misconfigurations.
compliance-drift-evals
Set up compliance exports, drift detection, evaluations, scoring, and learning analytics.
build-dashclaw
Contribute to the DashClaw codebase — architecture, scaffolding, tests, CI.