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/ajmichels/moneta-notes/claude-mdgit clone --depth 1 https://github.com/ajmichels/moneta-notesWrote 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/ajmichels/moneta-notes/claude-md)<a href="https://agentmods.dev/instructions/ajmichels/moneta-notes/claude-md"><img src="https://agentmods.dev/badge/instructions/ajmichels/moneta-notes/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 | $0.01995 | $0.01995 |
| Opus 5 | $0.00997 | $0.00997 |
| Sonnet 5 | $0.00399 | $0.00399 |
| Haiku 4.5 | $0.00199 | $0.00199 |
Grade A, and why
moneta-notes 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 4d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read README.md first for the full architecture and tool specs — this file is about how to build
it, not what to build.
docs/specs/ vs. docs/plans/
docs/specs/S0xx-*.mdare living documentation. They're the contract for what each subsystem does and why — update them in place as behavior changes (don't leave them describing stale behavior, and don't fork a new spec number for a change to something already specified).docs/plans/S0xx-*.mdare disposable. They're step-by-step execution checklists written for agentic implementation of a spec, not a reference anyone should need afterward — any rationale worth keeping belongs in the corresponding spec, not the plan. Checkbox state in these files isn't reliably maintained during implementation, so don't use it to judge completion — verify against the actual repo (does the code exist, does it match the spec, do the tests pass) instead.- Once a plan's spec is implemented and verified, delete the plan file. Keeping it around past that point only invites drift between plan and reality.
docs/*.md — user-facing guides
docs/installation.md, docs/usage.md, docs/process-management.md, and docs/uninstallation.md are
living documentation too, same rule as docs/specs/: keep them in sync with actual behavior, don't let
them drift. They're linked from the README's "Documentation" table so they're the first thing a reader
on GitHub reaches. Update the relevant page(s), in the same change, whenever you touch:
scripts/install.sh/scripts/uninstall.sh(steps, prompts, what gets created/removed) →docs/installation.md/docs/uninstallation.md.src/cli/main.js's command surface (new command, new/changed flag, changed output shape) →docs/usage.md.src/cli/daemon.js,src/indexer/daemon.js's launchd wiring, orlaunchd/*.plist.template(daemon control, log file layout, rotation policy) →docs/process-management.md.src/mcp/tools.js's tool list (added/removed/renamed MCP tool) →docs/usage.md's MCP section.
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.
- 4d ago First seen · 129 lines · 1,995 tokens per session scan A 4cbe9da3f607
moneta-notes CLAUDE.md is an instructions file published in the GitHub repository ajmichels/moneta-notes (0 stars, last pushed today), licensed Apache-2.0. It adds 1,995 tokens to every session, about $0.0100 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).
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).