Borrowing it
Nothing to install: this file belongs to Activ8-AI/Teamwork-MCP. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Activ8-AI/Teamwork-MCP/main/CLAUDE.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/claude-md)<a href="https://agentmods.dev/instructions/activ8-ai/teamwork-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/activ8-ai/teamwork-mcp/claude-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.1 | $0.00900 | $0.00900 |
| Opus 5 | $0.00450 | $0.00450 |
| Sonnet 5 | $0.00180 | $0.00180 |
| Haiku 4.5 | $0.00090 | $0.00090 |
Grade A, and why
Teamwork-MCP CLAUDE.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 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — @vizioz/teamwork-mcp
Charter binding: Activ8 AI Operational Execution & Accountability Charter (v1.5).
What to read first
docs/SOURCES-OF-TRUTH.md(this repo)docs/AUDIENCE-SURFACE-CONTRACT.md(this repo)- Central canonical SSOT map:
https://github.com/Activ8-AI/activ8-ai-unified-mcp-serveratdocs/SOURCES-OF-TRUTH.md
Output contract
Progress | Evidence | Blockers
Execution Rule
- Obvious-Answer Question Elimination Rule applies.
- If the next action is already clear, execute it instead of asking.
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 established work whenever possible; create new only when no suitable precedent exists.
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 Contract
- Validate with
npm run operationalize:build. - Run
npm run operationalize:repo -- --with-syncin closeout-capable flows when Notion is available.
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 · 78 lines · 900 tokens per session scan A 30d94c6ff02d
Teamwork-MCP CLAUDE.md is an instructions file published in the GitHub repository Activ8-AI/Teamwork-MCP (0 stars, last pushed today), licensed MIT. It adds 900 tokens to every session, about $0.0045 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
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.