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/callibrity/mocapi/claude-mdgit clone --depth 1 https://github.com/callibrity/mocapiWhat 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 | $0.01403 | $0.01403 |
| Opus 5 | $0.00701 | $0.00701 |
| Sonnet 5 | $0.00281 | $0.00281 |
| Haiku 4.5 | $0.00140 | $0.00140 |
Grade A, and why
mocapi 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 2d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude notes for mocapi
Project-specific overrides and additions. Global workflow, code-quality, and
OSS release process live in ~/CLAUDE.md (see # OSS Release Process there).
Workflow
Never write or edit code without being explicitly told to do so! You may ask if you are allowed to make changes, but do not do so unless I explicitly confirm.
When committing and pushing changes to CLAUDE.md only, include [skip ci] in the commit message to avoid triggering CI.
Documentation layout
Docs live under docs/ in three trees:
docs/guides/— user-facing how-tos for library consumers.docs/design/— living design docs describing the current architecture; updated in lockstep with the code.docs/adr/— Architecture Decision Records (point-in-time, status: Accepted/Superseded/etc.). Template atdocs/adr/_template.md.
The Ralph spec workflow has been retired; the historical specs that produced 0.1.0 → 0.17.0 were mined for ADRs and removed from the tree.
New non-trivial work follows the superpowers SDD pipeline — see
docs/superpowers/README.md for when it applies
and where spec/plan artifacts live.
When a change requires an ADR + design-doc update (rule)
Before writing code for an architecturally significant change, stop and produce two artifacts. "Architecturally significant" means the change falls into any of these buckets:
- A new module, or removal/merger of an existing module.
- A new SPI (interface intended for users to implement) or a backwards-incompatible change to an existing SPI.
- A new transport, or a change to the
McpServer↔McpTransportcontract. - A change to handler discovery, customizer composition, the stratum ordering, or the descriptor pattern.
- A change to session storage, mailbox/journal usage, or the Substrate SPI contract.
- A change to the authorization model (filter chains, Guard semantics,
McpTokenStrategy, RFC 9728 metadata shape). - A change to what mocapi declares not implemented in
docs/adr/0018-*.md(adding/removing an item from the list). - A change to declared MCP capabilities (
subscribe,listChanged, etc.).
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.
- 2d ago First seen · 116 lines · 1,403 tokens per session scan A 7a0a3a443493
mocapi CLAUDE.md is an instructions file published in the GitHub repository callibrity/mocapi (2 stars, last pushed 19d ago), licensed Apache-2.0. It adds 1,403 tokens to every session, about $0.0070 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
activepieces AGENTS.md
AGENTS.md instructions for activepieces/activepieces, covering activepieces, architecture (non-obvious rules), coding conventions, query error handling and key utilities (@activepieces/shared).
activepieces CLAUDE.md
Claude Code instructions for activepieces/activepieces, covering activepieces, architecture (non-obvious rules), coding conventions, query error handling and key utilities (@activepieces/shared).
trufflesqueak AGENTS.md
Instructions for hpi-swa/trufflesqueak, covering trufflesqueak agent reference, preflight checks, setup, install dependencies (ubuntu 24.04) and install oracle graalvm matching the current suite version.
gradle-mcp AGENTS.md
Instructions for rnett/gradle-mcp, covering gradle mcp project memory, primacy zone: fundamental mandates, technical standards (openspec), build & test commands and misc tips.
mcp-server-fuzzer AGENTS.md
Instructions for Agent-Hellboy/mcp-server-fuzzer, covering ai agent instructions, branch creation, commit message style, lint and tests and tox venv setup.
raindrop-mcp dxt.instructions.md
Instructions for adeze/raindrop-mcp: I want to build this as an MCP Bundle, abbreviated as "MCPB". Please follow these steps.