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/catlog22/Claude-Code-WorkflowWrote 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/commands/catlog22/claude-code-workflow/monitor)<a href="https://agentmods.dev/commands/catlog22/claude-code-workflow/monitor"><img src="https://agentmods.dev/badge/commands/catlog22/claude-code-workflow/monitor/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/commands/catlog22/claude-code-workflow/monitor"><img src="https://agentmods.dev/badge/commands/catlog22/claude-code-workflow/monitor.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.00000 | $0.01980 |
| Opus 5.5 | $0.00000 | $0.00792 |
| Sonnet 5.5 | $0.00000 | $0.00396 |
| Haiku 4.5 | $0.00000 | $0.00198 |
Grade A, and why
monitor 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.
How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monitor Pipeline
Event-driven pipeline coordination. Beat model: coordinator wake -> process -> spawn -> STOP.
Constants
- SPAWN_MODE: background
- ONE_STEP_PER_INVOCATION: true
- FAST_ADVANCE_AWARE: true
- WORKER_AGENT: team-worker
Handler Router
| Source | Handler |
|---|---|
| Message contains [analyzer], [designer], [refactorer], [validator], [reviewer] | handleCallback |
| Message contains branch tag [refactorer-B01], etc. | handleCallback (branch-aware) |
| Message contains pipeline tag [analyzer-A], etc. | handleCallback (pipeline-aware) |
| "consensus_blocked" | handleConsensus |
| "capability_gap" | handleAdapt |
| "check" or "status" | handleCheck |
| "resume" or "continue" | handleResume |
| All tasks completed | handleComplete |
| Default | handleSpawnNext |
handleCallback
Worker completed. Process and advance.
- Parse message to identify role, task ID, and branch/pipeline label:
| Message Pattern | Branch Detection |
|---|---|
[refactorer-B01] or task ID REFACTOR-B01 |
Branch B01 (fan-out) |
[analyzer-A] or task ID ANALYZE-A01 |
Pipeline A (independent) |
[analyzer] or task ID ANALYZE-001 |
No branch (single) |
- Mark task as completed:
TaskUpdate({ taskId: "<task-id>", status: "completed" }) - Record completion in session state
- CP-2.5 check (auto/fan-out mode only):
- If completed task is DESIGN-001 AND parallel_mode is
autoorfan-out: - Execute CP-2.5 Branch Creation from dispatch.md
- After branch creation, proceed to handleSpawnNext (spawns all REFACTOR-B* in parallel)
- STOP after spawning
- If completed task is DESIGN-001 AND parallel_mode is
- Check stage checkpoints:
| Completed Task | Checkpoint | Action |
|---|---|---|
| ANALYZE-001 / ANALYZE-{P}01 | CP-1 | Notify user: architecture report ready |
| DESIGN-001 / DESIGN-{P}01 | CP-2 | Notify user: refactoring plan ready |
| DESIGN-001 (auto/fan-out) | CP-2.5 | Execute branch creation, notify with branch count |
| VALIDATE-* or REVIEW-* | CP-3 | Check verdicts per branch (see Review-Fix Cycle) |
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 · 217 lines · 0 tokens per session scan A 4d9b242f7ee3
monitor is a command published in the GitHub repository catlog22/Claude-Code-Workflow (2,120 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,980 tokens. 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-09-03.
Other commands, from other repositories
session-list
List recent sessions from the project ledger and offer to view one.
jira
Retrieve a Jira ticket, analyze requirements, update status, or add comments. Uses the jira-integration skill and MCP or REST API.
wtfp:contribute
Guide a bounded WTF-P contribution from branch creation through a reviewable change request.
gofer_hydrate
Reverse-engineer specification from existing code (Hydration).
gofer:check-workspace
Check whether this repo is initialized for Gofer and explain any missing or stale scaffold.
4-finalize
Finalizes a reviewed thread, updates project documentation, and handles cleanup.