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.
git clone --depth 1 https://github.com/anshulixyz/multi-agent-loop-kitWrote 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/rules/anshulixyz/multi-agent-loop-kit/03-journal-format)<a href="https://agentmods.dev/rules/anshulixyz/multi-agent-loop-kit/03-journal-format"><img src="https://agentmods.dev/badge/rules/anshulixyz/multi-agent-loop-kit/03-journal-format/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/anshulixyz/multi-agent-loop-kit/03-journal-format"><img src="https://agentmods.dev/badge/rules/anshulixyz/multi-agent-loop-kit/03-journal-format.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00188 | $0.00188 |
| Opus 5.5 | $0.00075 | $0.00075 |
| Sonnet 5.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 1mo 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.
- 1mo 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 4mo ago), licensed MIT. It adds 188 tokens to every session, about $0.0008 per session on Opus 5.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
project-epic-template-cursorrules-prompt-file
Cursor rules for project development with epic template integration.
client-workflow-bootstrap
Cursor rule "client-workflow-bootstrap" from ulises-jeremias/agent-toolkit, covering agent vs skill rule — why agent (cite clause), when to use vs holistic, caller / skills / handoff, interview process and gate before generating.
swamr-state-manager
Swamr State Manager — tracks task progress, manages the execution pipeline, handles retries and escalation. Maintains swamr/state.json as the single source of truth for swarm progress.
state-transition-rule
A rule describing a request status flow from pending to approved and then to item creation. It is written in Chinese.
tasks
Guidelines for implementing task management operations.
moo-tasks
You are connected to the Moo Tasks MCP server. Every code change you make is tracked as a Moo task.