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/neethanwu/joa/claude-mdgit clone --depth 1 https://github.com/neethanwu/joaWrote 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/neethanwu/joa/claude-md)<a href="https://agentmods.dev/instructions/neethanwu/joa/claude-md"><img src="https://agentmods.dev/badge/instructions/neethanwu/joa/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.00408 | $0.00408 |
| Opus 5 | $0.00204 | $0.00204 |
| Sonnet 5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
joa 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.
What it actually says
joa — CLAUDE.md
Runtime
- Dev tooling: Bun —
bun test,bun install,bunx biome. - Published CLI: Node.js —
tscbuild todist/, shebang#!/usr/bin/env node. - SQLite: Runtime shim in
db.ts—bun:sqliteunder Bun,better-sqlite3under Node.js.
Architecture
- Write order: JSONL first, SQLite second. JSONL is source of truth.
- Session ID: no module-level singleton.
sessionId()is a generator. Callers pass it throughLogContext. - Three-layer module architecture:
- Layer 1 (Foundations):
errors,ids,config— no internal deps - Layer 2 (Storage):
time,entry,journal,db,sync,context— depends on Layer 1 only - Layer 3 (Operations):
formatters,log,query,status— depends on Layer 1 + 2
- Layer 1 (Foundations):
Code Standards
- No
anywithout a JSDoc comment explaining why. - No SQLite driver imports outside
db.ts. - Core library (
src/core/) has no CLI or MCP imports.
Testing
- Tests use in-memory SQLite (
new Database(":memory:")) and temp dirs. - Run tests:
bun test
Lint / Format
- Run lint:
bunx biome check . - Fix lint:
bunx biome check --write . - Typecheck:
bunx tsc --noEmit
Important Constraints
- FTS escaping: always escape user-provided search strings before passing to SQLite FTS.
- Tag filtering: uses
json_each()for exact match. Tags must not contain"or\characters (validated at write time).
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 · 33 lines · 408 tokens per session scan A e7d1970b3e51
joa CLAUDE.md is an instructions file published in the GitHub repository neethanwu/joa (1 stars, last pushed 4mo ago), licensed MIT. It adds 408 tokens to every session, about $0.0020 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.