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 instructions/activ8-ai/teamwork-mcp/agents-mdgit clone --depth 1 https://github.com/Activ8-AI/Teamwork-MCPWrote 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/instructions/activ8-ai/teamwork-mcp/agents-md)<a href="https://agentmods.dev/instructions/activ8-ai/teamwork-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/activ8-ai/teamwork-mcp/agents-md.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.01062 | $0.01062 |
| Opus 5 | $0.00531 | $0.00531 |
| Sonnet 5 | $0.00212 | $0.00212 |
| Haiku 4.5 | $0.00106 | $0.00106 |
Grade A, and why
Teamwork-MCP AGENTS.md 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — @vizioz/teamwork-mcp
Charter binding: Activ8 AI Operational Execution & Accountability Charter (v1.5).
Source of truth
- Local routing map:
docs/SOURCES-OF-TRUTH.md - Local audience + surface contract:
docs/AUDIENCE-SURFACE-CONTRACT.md - Central canonical policy:
https://github.com/Activ8-AI/activ8-ai-unified-mcp-serverat.github/ai-agent-policy.md
Output contract
Progress | Evidence | Blockers
Obvious-Answer Question Elimination Rule
- Do not ask for confirmation when the requested action is already clear.
- Execute the next obvious step and present the result.
Seek-First Planning Gate
- No action begins without a plan.
- Verify in order: Notion first, then repo, then local/runtime files.
- Search for existing artifacts before touching or proposing anything new.
- Build on lineage before create-new.
Seek First to Understand + Verify What Exists
- Seek First to Understand: before answering, deciding, or acting, gather context and ensure full comprehension.
- Verify what exists in Notion: never assume. Check Notion first. Confirm presence, accuracy, and status of relevant information before proceeding.
- Search for existing artifacts: look for relevant databases, pages, prior work, and connected surfaces before touching, modifying, or proposing anything new.
- Build on established work: extend, refine, or elevate what exists. Respect artifact lineage.
- Create new only when necessary: new artifacts or structures only when no suitable reference, structure, or precedent exists.
- Fail closed on deviation: if verification is missing, the user correction changes the path, or drift is detected, stop, surface the mismatch, and restart from verified state.
Managed Repo Operationalization
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 · 91 lines · 1,062 tokens per session scan A 95f9e65131b8
Teamwork-MCP AGENTS.md is an instructions file published in the GitHub repository Activ8-AI/Teamwork-MCP (0 stars, last pushed 5mo ago), licensed MIT. It adds 1,062 tokens to every session, about $0.0053 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 instructions, from other repositories
ESAA-Core AGENTS.md
Instructions for elzobrito/ESAA-Core, covering agents.md — contrato operacional codex/esaa, 1. autoridade e termos, 2. cli e runner, ou configure o runner uma vez por sessão and 3. concorrência.
idd-skill idd-resume.instructions.md
Instructions for kurone-kito/idd-skill, covering idd — resume phase, required inputs, step 0 — route classifier, operator-present release and step 1 — identify claim state.
tmetric-minimal-mcp CLAUDE.md
Claude Code instructions for guglielmo/tmetric-minimal-mcp, covering claude.md, development commands, project architecture, file structure and core architecture patterns.
shelly-forge CLAUDE.md
Claude Code instructions for mslavov/shelly-forge, covering documentation usage guidelines, critical: framework-first reading order, 📚 mandatory reading order, pre-task protocol and post-task protocol.
vibelive AGENTS.md
AGENTS.md instructions for pooriaarab/vibelive, covering agents.md, repository context, pull requests, cloud agents (cursor) and install & test.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).