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 rules/anshulixyz/multi-agent-loop-kit/03-journal-formatgit clone --depth 1 https://github.com/anshulixyz/multi-agent-loop-kitWhat 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.00188 | $0.00188 |
| Opus 5 | $0.00094 | $0.00094 |
| Sonnet 5 | $0.00038 | $0.00038 |
| Haiku 4.5 | $0.00019 | $0.00019 |
Grade A, and why
03-journal-format 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 3d 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
Journal rules
Each agent maintains:
agents-status/<codename>.md
Update it:
- at session start
- before stopping
- when blocked
- after shipping
- after creating approval/proposal
- after accepting/skipping Beacon task
Use exactly this schema:
## Now
## Just shipped
## Blocked / waiting on
## Discussion needed
## Approvals open
## Proposals open
## Next
## Notes
Write nothing in empty sections.
Never coordinate meaningful build state through private chat. Put it in journals, approvals, proposals, or task briefs.
Use these prefixes:
[task] <agent>: <action>
[approval] operator: <approval path>
[setup] operator: <setup action>
[launch] operator: <demo/launch action>
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.
- 3d ago First seen · 46 lines · 188 tokens per session scan A 555bf246b4a2
03-journal-format is a cursor rule published in the GitHub repository anshulixyz/multi-agent-loop-kit (5 stars, last pushed 2mo ago), licensed MIT. It adds 188 tokens to every session, about $0.0009 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 cursor rules, from other repositories
handoff
Export a Waybill Bundle by default, or import one when explicitly requested.
waybill
Alias for the Waybill handoff workflow.
example
Missing project/docs/does-not-exist.md. Also broken src/does-not-exist.ts.
tech-stack
Cursor rule "tech-stack" from yu-iskw/coding-agent-fabric, covering tech stack, pnpm workspace & monorepo best practices, common commands, workspace protocol and dependency management.
frontend
UI/component conventions. Apply when building or changing user-facing frontend code.
cursorrules
Always use TypeScript.