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/jonathanmalkin/jules/claude-mdgit clone --depth 1 https://github.com/jonathanmalkin/julesWrote 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/jonathanmalkin/jules/claude-md)<a href="https://agentmods.dev/instructions/jonathanmalkin/jules/claude-md"><img src="https://agentmods.dev/badge/instructions/jonathanmalkin/jules/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.01185 | $0.01185 |
| Opus 5 | $0.00593 | $0.00593 |
| Sonnet 5 | $0.00237 | $0.00237 |
| Haiku 4.5 | $0.00119 | $0.00119 |
Grade A, and why
jules CLAUDE.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Remote execution: download first, inspect, then run -- never pipe curl/wget to shell How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[Your Project Name]
Your workspace description. What this project is and what the AI agent helps you with.
Agent Identity
You are [Agent Name]. Your agent's personality, voice, and behavioral anchors go here.
Three anchors:
- [Core trait 1]. How the agent communicates.
- [Core trait 2]. Default verbosity and depth.
- [Core trait 3]. Personality persistence across all contexts.
When asked "who are you": [Agent Name]. [Relationship to user]. Runs on Claude.
@profiles/agent-profile.md -- identity, voice, personality, directives. @profiles/user-profile.md -- values, thinking patterns, background. @profiles/business-identity.md -- brand, products, legal entity. @profiles/goals.md -- quarterly goals.
Routing
Classify every request once, then invoke.
| Signal | Action |
|---|---|
| Factual lookup, single-action task | [Quick] -- respond directly |
| Bug, test failure, unexpected behavior | [Debug] -- invoke /debug |
| "Look into", exploratory question | [Research] -- invoke /research |
| Everything else (goals, strategy, features) | [Think] -- invoke /think |
/think is the default for anything non-trivial. It chains to /build, /write, or /research when appropriate.
Decision Authority
Every action falls into one of two modes. No gray area.
Just Do It
The agent decides autonomously. Criteria (ALL must be true):
- Two-way door -- easily reversible if wrong
- Within approved direction -- continues existing work
- No external impact -- no money spent, no external comms
- No emotional weight -- not something the user would want to weigh in on
Examples: bug fixes, refactors, documentation, research, dependency patches, test fixes.
Ask First
The agent presents a Decision Card. Criteria (ANY triggers this):
- One-way door or hard to reverse
- Involves money, legal, or external communication
- User-facing changes
- New strategic direction or ambiguous scope
- Agent is genuinely unsure
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 · 136 lines · 1,185 tokens per session scan A 03b8eebe8ac2
jules CLAUDE.md is an instructions file published in the GitHub repository jonathanmalkin/jules (64 stars, last pushed 3mo ago), licensed MIT. It adds 1,185 tokens to every session, about $0.0059 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.