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 skills add mnzralee/claude-multi-agent-architecture --skill work-recordinggit clone --depth 1 https://github.com/mnzralee/claude-multi-agent-architectureWrote 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/skills/mnzralee/claude-multi-agent-architecture/work-recording)<a href="https://agentmods.dev/skills/mnzralee/claude-multi-agent-architecture/work-recording"><img src="https://agentmods.dev/badge/skills/mnzralee/claude-multi-agent-architecture/work-recording/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/skills/mnzralee/claude-multi-agent-architecture/work-recording"><img src="https://agentmods.dev/badge/skills/mnzralee/claude-multi-agent-architecture/work-recording.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.00057 | $0.04278 |
| Opus 5 | $0.00028 | $0.02139 |
| Sonnet 5 | $0.00011 | $0.00856 |
| Haiku 4.5 | $0.00006 | $0.00428 |
Grade A, and why
work-recording 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 662 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work Recording Skill
Transform development sessions into compelling engineering stories that capture not just what happened, but why it mattered and what was learned.
Location: write to YOUR OWN journal
Each developer has their own append-only journal directory. Write to the authoring developer's namespace, never to another developer's.
you write to: docs/workrecords/work-record-YYYY-MM-DD.md
[CUSTOMIZE: adjust the path to match your project's docs layout. A common convention is docs/<your-name>/workrecords/work-record-YYYY-MM-DD.md for multi-developer projects.]
The path is determined by WHO is writing, not by which feature, service, or repo the work touched. The storytelling voice below requires first-person "I"; two developers cannot share an "I", so they cannot share a journal file. Cross-developer coordination lives at the spec, roadmap, and ADR layer, not by mingling daily journals.
See .claude/rules/work-records.md for the full per-developer-path rule, if your project uses one.
Philosophy: The Engineering Story
Work records are not logs. They are stories.
Every session is a journey with:
- A beginning (context, challenge)
- A middle (investigation, discovery, implementation)
- An end (resolution, lessons learned)
The best work records read like a senior engineer explaining their day to a colleague over coffee: technical, insightful, and memorable.
The Journal Principle: Write It Like Lecture Notes
Work records serve a dual purpose: they are both a professional engineering journal and lecture notes for the developer's future self. When writing, imagine revisiting this record months later to understand what happened, why, and what was learned.
What to Capture
Brainstorming and critical-thinking moments. When multiple approaches are considered, document the reasoning chain: what options surfaced, what tradeoffs were weighed, and why one path was chosen over others. The rejected alternatives matter as much as the chosen one because they encode the constraints that shaped the decision.
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.
- 10d ago First seen · 662 lines · 57 tokens per session scan A 94fcb16d4489
work-recording is a skill published in the GitHub repository mnzralee/claude-multi-agent-architecture (6 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 4,278 once invoked, about $0.0003 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 skills, from other repositories
coordinate-agents
Route Codex-native multi-agent orchestration in a Git repository through a local-first, recoverable Agent Bus. Use for role-based planning, task execution, review, recovery, adapters, and human-gated release workflows. The plugin supports Codex CLI, Google Antigravity CLI, Claude, and other configured coding agents.…
coordinate-task
Run a Coordinate Agents Task from requirement clarification through planning, implementation, review, and the human release gate. Hide Agent Bus transport details behind the durable Task API.
coordinate-recover
Diagnose and safely resume Coordinate Agents Tasks after executable failure, non-zero exit, timeout, stale claim, processing message, or Implementer ERROR. Recovery is explicit and never an automatic retry loop.
coordinate-setup
Discover coding CLIs on the current computer and configure a Coordinate Agents implementation agent. Use for setup, executable checks, registered agents, user-level configuration, and project-over-user precedence.
coordinate-review
Review a Coordinate Agents implementation as the Codex Reviewer. Verify the real commit, diff, tests, validation evidence, and specification without modifying the Implementer's product code.
antigravity-agents
This document manages all domain-specific .agents/skills/ /SKILL.md files.