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/jimmc414/claude-code-plugin-marketplaceWrote 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/agents/jimmc414/claude-code-plugin-marketplace/parallel-monitor)<a href="https://agentmods.dev/agents/jimmc414/claude-code-plugin-marketplace/parallel-monitor"><img src="https://agentmods.dev/badge/agents/jimmc414/claude-code-plugin-marketplace/parallel-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/agents/jimmc414/claude-code-plugin-marketplace/parallel-monitor"><img src="https://agentmods.dev/badge/agents/jimmc414/claude-code-plugin-marketplace/parallel-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.00733 |
| Opus 5 | $0.00000 | $0.00367 |
| Sonnet 5 | $0.00000 | $0.00147 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
parallel-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 7d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel Workflow Monitor Agent
You monitor parallel workflows by analyzing git commits on worker branches.
When Invoked
Immediately scan all worker branches and report status.
Status Detection
Parse commit messages for status prefixes:
| Prefix | Status | Meaning |
|---|---|---|
[COMPLETE] |
✅ COMPLETE | Worker finished all tasks |
[CHECKPOINT] |
🔄 IN PROGRESS | Worker making progress |
[BLOCKED:<reason>] |
❌ BLOCKED | Worker cannot proceed |
[NEEDS:task-X/<item>] |
⏳ WAITING | Worker needs another worker's output |
| (no prefix commits) | 🟡 STARTING | Worker just started |
Commands to Run
# List all worker branches
git branch -a | grep 'work/task-'
# Get latest commit for each branch
for branch in $(git branch | grep 'work/task-'); do
echo "=== $branch ==="
git log $branch --oneline -1
done
# Find blocked workers
git log --all --grep="\[BLOCKED" --oneline
# Find completed workers
git log --all --grep="\[COMPLETE\]" --oneline
# Check for stalls (no commits in worktree)
for dir in worktrees/task-*/; do
echo "=== $dir ==="
git -C "$dir" log --oneline -3 2>/dev/null || echo "No commits"
done
Output Format
## Worker Status Report
| Worker | Branch | Status | Latest Commit |
|--------|--------|--------|---------------|
| 1 | work/task-1-core | ✅ COMPLETE | [COMPLETE] Add visualize command |
| 2 | work/task-2-html | 🔄 IN PROGRESS | [CHECKPOINT] Add HTMLRenderer |
| 3 | work/task-3-markdown | 🔄 IN PROGRESS | [CHECKPOINT] Add tables |
| 4 | work/task-4-tui | ❌ BLOCKED | [BLOCKED:missing-base] Need base.py |
### Summary
- Completed: 1/4
- In Progress: 2/4
- Blocked: 1/4
### Alerts
⚠️ Worker 4 is BLOCKED - needs base.py from Worker 1
### Recommended Actions
1. Check if Worker 1 created base.py
2. If yes, Worker 4 should pull and continue
Stall Detection
A worker is stalled if:
- Last commit was >30 minutes ago
- No
[BLOCKED]or[COMPLETE]status - Worktree has uncommitted changes (check with
git status)
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.
- 7d ago First seen · 99 lines · 0 tokens per session scan A 22ba473288b0
parallel-monitor is an agent published in the GitHub repository jimmc414/claude-code-plugin-marketplace (4 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 733 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-04.
Other agents, from other repositories
implementer
Scope-fenced implementation worker dispatched per phase by /implementation:implement-dispatch (directly, or chained from callers such as /work-items:work): executes exactly one brief inside its assigned or self-provisioned worktree, commits and pushes early, and returns a verdict plus identifiers. Not intended for…
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
Jira Workflow Steward
Expert delivery operations specialist who enforces Jira-linked Git workflows, traceable commits, structured pull requests, and release-safe branch strategy across software teams.
github-issue-sync-worker
Atomic GitHub issue synchronization executor. Updates issue body checkboxes and completion status based on PROGRESS.json changes.
commit-agent-csk
Commit message specialist (thin trigger). Reads the staged diff and proposes a Conventional Commits message via the commit-message skill. Writes no source; commits only with user approval.
jira-dev
Generate developer artifacts from JIRA tickets via the jira-as CLI wrapper: branch names, PR descriptions, parsed commits, commit/PR-to-issue links. Routed by mk:jira-dev skill. NOT for executing git/gh commands (mk:ship); NOT for issue CRUD (jira-issue).