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/agentience/tribal_mcp_server/claude-mdgit clone --depth 1 https://github.com/agentience/tribal_mcp_serverWrote 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/agentience/tribal_mcp_server/claude-md)<a href="https://agentmods.dev/instructions/agentience/tribal_mcp_server/claude-md"><img src="https://agentmods.dev/badge/instructions/agentience/tribal_mcp_server/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.00691 | $0.00691 |
| Opus 5 | $0.00345 | $0.00345 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
tribal_mcp_server 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 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tribal - CLAUDE.md
Build/Lint/Test Commands
- Setup:
uv pip install -e .- Install package in development mode - Install dependencies:
uv pip install -r requirements.txt - Install dev dependencies:
uv pip install -r requirements-dev.txt - Create/update venv:
uv venv - Run server:
tribalorpython -m mcp_server_tribal.mcp_app - Lint:
ruff check . - Type check:
mypy . - Run tests:
pytest - Run single test:
pytest tests/path_to_test.py::test_name
MCP Server Notes
Docker Configuration
- Docker container name:
tribal - Docker exposed port: 8000 (mapped to internal port 5000)
- Docker image name:
tribal-mcp - Current state: Running in standard mode
FastMCP Version Information
- Server: Using FastMCP 1.3.0+
- Modern version with improved API
- Supports the
mcp.run(transport='stdio')interface for stdio MCPs - No need for the
@mcp.handle_executiondecorator anymore
Claude Integration
- Claude Code CLI: Configure via
claude mcp add tribal tribal - For global installation:
claude mcp add --scope global tribal tribal - Server runs on demand when Claude needs it (stdio protocol)
Code Style Guidelines
- Framework: FastAPI for REST API development
- Imports: Group imports (stdlib, 3rd-party, local) with blank lines between groups
- Formatting: Black for code formatting, line length 88
- Types: Use type annotations for all function definitions
- Naming: Snake_case for variables/functions, PascalCase for classes
- Error Handling: Use explicit exception handling with appropriate status codes
- Documentation: All public APIs should have docstrings in Google format
- Structure: Organize code into models, services, api, and utils modules
Editor Config
- Use 4 spaces for indentation
- UTF-8 encoding for all files
MCP Integration Instructions
Error Tracking Integration
Claude should automatically load and use the MCP integration for tracking errors and solutions.
At the start of each session, Claude should:
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 · 77 lines · 691 tokens per session scan A 8e7e6b392709
tribal_mcp_server CLAUDE.md is an instructions file published in the GitHub repository agentience/tribal_mcp_server (4 stars, last pushed 10mo ago), licensed MIT. It adds 691 tokens to every session, about $0.0035 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
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).
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 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.
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.