Borrowing it
Nothing to install: this file belongs to humandesignai/human-design-ai-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/humandesignai/human-design-ai-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/humandesignai/human-design-ai-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/humandesignai/human-design-ai-mcp/claude-md)<a href="https://agentmods.dev/instructions/humandesignai/human-design-ai-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/humandesignai/human-design-ai-mcp/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/humandesignai/human-design-ai-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/humandesignai/human-design-ai-mcp/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.00299 | $0.00299 |
| Opus 5 | $0.00150 | $0.00150 |
| Sonnet 5 | $0.00060 | $0.00060 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
human-design-ai-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.
What it actually says
human-design-ai-mcp
Feature registry (required)
The canonical list of every HumanDesign.ai feature, which plans include it, and what
enforces that lives in the hdai-feature-registry repo (under your Projects folder;
find it by name, the folder layout moves). Read it before describing, pricing or gating any
feature. It outranks this repo's own docs and any marketing copy.
This repo owns api-mcp (plugin distribution) in that registry.
When you ship a customer-visible change (new feature, rename, changed entitlement, changed
limit, changed price, retirement) update the registry in the SAME change and set that
entry's lastVerified to today, then run npm run check there. A change that alters
what members can do is not finished until the registry matches it.
If the registry says unknown, or an entry carries a contradiction with
needsHumanDecision: true, say so and stop. Do not infer a plan, price, limit or quota
the registry does not state. Read plans.yaml's traps: block before writing any
entitlement gate; it records the identifier mistakes that have already caused real defects.
Then consider an announcement: /announce-feature diffs the registry, works out which
plans each change is news for, and drafts the newsletter, social posts and community post.
It stops at drafts; nothing sends without Kyle.
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 · 25 lines · 299 tokens per session scan A 9b026ca552d4
human-design-ai-mcp CLAUDE.md is an instructions file published in the GitHub repository humandesignai/human-design-ai-mcp (1 stars, last pushed 4d ago), licensed MIT. It adds 299 tokens to every session, about $0.0015 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-09-04.
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).
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.
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).