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/doug/jjj/agents-mdgit clone --depth 1 https://github.com/doug/jjjWhat 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.00464 | $0.00464 |
| Opus 5 | $0.00232 | $0.00232 |
| Sonnet 5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
jjj AGENTS.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.
What it actually says
Agent instructions
This repository is jjj, a project tracker built on Jujutsu. It is also
managed with jjj — problems, solutions, and critiques live in the jjj
bookmark alongside the code.
Before you write anything
Set an identity. Without it every agent shares the repository owner's identity, so work claims overwrite each other and per-agent queues do not work:
export JJJ_USER=<your agent name>
jjj whoami --json # confirm it took effect
Read this first
skills/jjj/SKILL.md — how to use and collaborate through jjj: the machine
interface, the single-agent loop, and the multi-agent patterns (work claiming,
rival conjectures, adversarial review, collision avoidance, pods). It is checked
against the real CLI by tests/skill_test.rs, so it does not drift.
For working on jjj's own code, CLAUDE.md covers the architecture, storage
model, and build commands.
House rules
- Use ids, not titles, in anything scripted. Fuzzy title matching resolves to
whatever uniquely matches today. Read ids from
--json. - Never
--forcepast a critique.jjj solution approve --forcebypasses the one mechanism that makes review real. - Automation rules are machine-local (
.jj/jjj-meta/automation.toml) and are deliberately never synced. Do not move them intoconfig.toml; that file travels through the shared bookmark and a rule there would execute on every collaborator's machine. jjj doctoris the first thing to run when something looks wrong, and the right thing to attach to a bug report.
Verifying changes to this repository
cargo fmt --check
cargo clippy --all-targets --all-features -- -D warnings
cargo test
Behaviour that users see should be covered by an executable journey in
journeys/ — they are markdown, they run as tests, and they double as the
documentation. RELEASE.md lists the checks CI cannot make.
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 · 51 lines · 464 tokens per session scan A abe20002c3c7
jjj AGENTS.md is an instructions file published in the GitHub repository doug/jjj (11 stars, last pushed 3d ago), licensed Apache-2.0. It adds 464 tokens to every session, about $0.0023 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-30.
Other instructions, from other repositories
kaneo AGENTS.md
AGENTS.md instructions for usekaneo/kaneo, covering kaneo agent guide, principles, architecture, boundaries that must hold and follow a change through.
kaneo CLAUDE.md
Claude Code instructions for usekaneo/kaneo, a project described as: 🎯 All you need. Nothing you don't. Open source project management that works for you, not against you.
veritas-kanban AGENTS.md
Instructions for BradGroux/veritas-kanban, covering agents.md — canonical agent instructions for veritas kanban, runtime requirements, repository layout, essential commands and install.
veritas-kanban CLAUDE.md
Instructions for BradGroux/veritas-kanban, covering claude.md — claude-specific supplement for veritas kanban, what changed in v2.1, lessons learned (claude-specific), security and architecture.
FlowBoard AGENTS.md
Instructions for rasimme/FlowBoard, covering flowboard — agent entry point, start here and where things live.
sideboard CLAUDE.md
Instructions for mmyslin/sideboard: Sideboard's own roadmap lives in GitHub Issues (mmyslin/sideboard). The project is GitHub-only — there is no roadmap.json / local-file mode.