Borrowing it
Nothing to install: this file belongs to elevanaltd/HestAI-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/elevanaltd/HestAI-MCP/main/CLAUDE.mdgit clone --depth 1 https://github.com/elevanaltd/HestAI-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/elevanaltd/hestai-mcp/claude-md)<a href="https://agentmods.dev/instructions/elevanaltd/hestai-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/elevanaltd/hestai-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.00791 | $0.00791 |
| Opus 5 | $0.00396 | $0.00396 |
| Sonnet 5 | $0.00158 | $0.00158 |
| Haiku 4.5 | $0.00079 | $0.00079 |
Grade A, and why
HestAI-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 7d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HestAI MCP Server
Python MCP server providing context management tools for Claude Code.
Quick Commands
Always use .venv/bin/python — the system python does not have project packages.
The .venv is created by the session startup hook (uv sync --all-extras).
# Quality gates (run before committing)
.venv/bin/python -m ruff check src tests scripts
.venv/bin/python -m black --check src tests scripts
.venv/bin/python -m mypy src
.venv/bin/python -m pytest
# Fix formatting
.venv/bin/python -m black src tests scripts
.venv/bin/python -m ruff check --fix src tests scripts
# Run specific test markers
.venv/bin/python -m pytest -m smoke # Fast sanity checks
.venv/bin/python -m pytest -m behavior # Behavioral tests (NOW)
.venv/bin/python -m pytest -m contract # Contract tests (SOON)
Governance: Bundled Hub vs .hestai-sys/
.hestai-sys/ is READ-ONLY runtime delivery. Changes there are lost on MCP server restart.
To modify agents, skills, patterns, cognitions, or specs persistently:
- Write to:
src/hestai_mcp/_bundled_hub/library/(committed source, packaged into MCP server) - Never modify:
.hestai-sys/directly (runtime copy, gitignored, overwritten on restart)
The MCP server copies _bundled_hub/ contents to .hestai-sys/ at startup. The flow is:
src/hestai_mcp/_bundled_hub/ → (packaged) → MCP server → (delivered) → .hestai-sys/
Domain Authority for Hub Changes
Changes to bundled hub artifacts MUST be delegated to the domain expert via oa-router:
- Agent changes → delegate to
agent-expert(agent structure, archetypes, capabilities) - Skill/pattern changes → delegate to
skills-expert(spec compliance, anchor kernels, discovery)
Do NOT modify skills or agent definitions directly — oa-router enforces blocking authority over these domains at runtime through the anchor ceremony process.
Core Files
src/hestai_mcp/mcp/server.py- MCP server entry pointsrc/hestai_mcp/mcp/tools/- MCP tool implementations (clock_in, clock_out, bind)src/hestai_mcp/ai/- AI client and provider abstractionssrc/hestai_mcp/schemas/- Pydantic schemassrc/hestai_mcp/_bundled_hub/- Governance source (agents, skills, patterns, cognitions)tests/- Test suite mirroring src/ structure.hestai/north-star/- Project North Star and component North Starsdocs/ARCHITECTURE.md- System architecture reference
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.
- 7d ago First seen · 75 lines · 791 tokens per session scan A 1411108de3a0
HestAI-MCP CLAUDE.md is an instructions file published in the GitHub repository elevanaltd/HestAI-MCP (0 stars, last pushed today), licensed Apache-2.0. It adds 791 tokens to every session, about $0.0040 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.
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.