Borrowing it
Nothing to install: this file belongs to Claire-s-Monster/pixi-task. 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/Claire-s-Monster/pixi-task/development/CLAUDE.mdgit clone --depth 1 https://github.com/Claire-s-Monster/pixi-taskWrote 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/claire-s-monster/pixi-task/claude-md)<a href="https://agentmods.dev/instructions/claire-s-monster/pixi-task/claude-md"><img src="https://agentmods.dev/badge/instructions/claire-s-monster/pixi-task/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/claire-s-monster/pixi-task/claude-md"><img src="https://agentmods.dev/badge/instructions/claire-s-monster/pixi-task/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.03494 | $0.03494 |
| Opus 5 | $0.01747 | $0.01747 |
| Sonnet 5 | $0.00699 | $0.00699 |
| Haiku 4.5 | $0.00349 | $0.00349 |
Grade A, and why
pixi-task 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 8d 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 — 489 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lean MCP Server Implementation Framework
Overview
This document provides a comprehensive framework for implementing "Lean MCP Servers" - a revolutionary approach to MCP server development that reduces context consumption by 95%+ while maintaining 100% functionality through the meta-tool pattern.
🚨 CRITICAL PROBLEM SOLVED
Traditional MCP Server Issue:
- Each MCP server exposes 10-50 verbose tool definitions
- Context consumption: 20-50K tokens per server
- With 10+ servers: 200K+ tokens just for tool definitions
- Result: Agents hit context limits before any real work begins
Lean MCP Solution:
- Expose only 3 meta-tools instead of 10+ verbose tools
- Context consumption: ~500 tokens per server (95%+ reduction)
- With 10+ servers: ~5K tokens total
- Result: Agents can focus on actual work, not parsing tool definitions
Architecture Pattern: Meta-Tool Discovery
The Three Meta-Tools
Every Lean MCP server exposes exactly these 3 meta-tools:
{
"discover_tools": {
"description": "Get available tools with minimal context consumption",
"parameters": {"pattern": "string"}
},
"get_tool_spec": {
"description": "Get full specification for specific tool",
"parameters": {"tool_name": "string"}
},
"execute_tool": {
"description": "Execute tool with parameters",
"parameters": {"tool_name": "string", "parameters": "object"}
}
}
Context Impact: ~500 tokens total (vs 20-50K for traditional)
Agent Workflow Pattern
# Step 1: Discover relevant tools (minimal context)
tools = mcp_server.discover_tools(pattern="session")
# Context: ~150 tokens
# Step 2: Get specification for chosen tool (on-demand)
spec = mcp_server.get_tool_spec("session_track_execution")
# Context: ~300 tokens
# Step 3: Execute tool with parameters
result = mcp_server.execute_tool("session_track_execution", {
"agent_name": "test-runner",
"step_data": {"phase": "start", "command": "pytest"}
})
# Context: Standard execution
# Total Context: ~500 tokens (vs 20-50K traditional)
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.
- 8d ago First seen · 489 lines · 3,494 tokens per session scan A 93ec349fa87c
pixi-task CLAUDE.md is an instructions file published in the GitHub repository Claire-s-Monster/pixi-task (0 stars, last pushed 12d ago), licensed MIT. It adds 3,494 tokens to every session, about $0.0175 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
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.
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).
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.