pixi-task: Instructions file for Claude Code

CLAUDE.md

pixi-task CLAUDE.md is an instructions file for Claude Code from Claire-s-Monster/pixi-task. It costs 3,494 tokens per session, scanned A, original, MIT.

A set of instructions for building MCP servers with three discovery tools instead of listing every tool at once. MCP is a way for an AI coding agent to use external tools.

In plain words
What is it for?
Use it as a design guide when implementing a lean MCP server and its tool-discovery workflow.
Why use it?
Large tool lists consume the agent’s working context before it can do useful work. This pattern keeps the initial description small while allowing the agent to discover detailed tools when needed.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md.

This is Claire-s-Monster/pixi-task's own configuration. It tells Claude Code how to work on pixi-task itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything pixi-task configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/Claire-s-Monster/pixi-task/development/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/Claire-s-Monster/pixi-task

Made for: Claude Code.

Wrote 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.

agentmods badge for pixi-task CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/claire-s-monster/pixi-task/claude-md/github.svg)](https://agentmods.dev/instructions/claire-s-monster/pixi-task/claude-md)
Your own site
<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.

agentmods 80×15 button for pixi-task CLAUDE.md

Your own site · 80×15
<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>
Per session 3,494 This file is loaded in full into every session.
When invoked 3,494 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 8d ago against content hash 93ec349fa87c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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.

CLAUDE.md · 489 lines

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)

Read the full file on GitHub · 489 lines

Changes

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.

  1. 8d ago First seen · 489 lines · 3,494 tokens per session scan A 93ec349fa87c

Subscribe to this mod's changes

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.

Related

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

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).

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

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.

deepseek-ai/deepseek-harness · 3,737 tokens