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/PounceAI/bob-controlWrote 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/plugins/pounceai/bob-control/claude-plugin)<a href="https://agentmods.dev/plugins/pounceai/bob-control/claude-plugin"><img src="https://agentmods.dev/badge/plugins/pounceai/bob-control/claude-plugin/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/plugins/pounceai/bob-control/claude-plugin"><img src="https://agentmods.dev/badge/plugins/pounceai/bob-control/claude-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
bob-companion 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
{
"name": "bob-companion",
"displayName": "Bob Companion",
"description": "Use Claude Code from any repo as the foreman and worker for the IBM Bob task board: provision, route, triage, and drain tasks Bob shares. Ships a self-contained MCP server.",
"version": "2.4.2",
"author": {
"name": "Joshua Gilbert"
},
"keywords": ["ibm-bob", "mcp", "tasks", "companion", "foreman", "worker", "ibm-i"]
}
What it installs
The manifest is a name and a version. 4 skills, 8 commands, 1 agent, 1 MCP server travel with it, and installing the plugin installs all of them — 591 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill bob-review A 108 tokens
- Skill bob-security A 103 tokens
- Skill bob-plan A 104 tokens
- Skill bob-refactor A 106 tokens
- Command bob-review-diff A 21 tokens
- Command bob-work A 19 tokens
- Command bob-new A 14 tokens
- Command bob-triage A 13 tokens
- Command bob-next A 15 tokens
- Command bob-route A 14 tokens
- Command bob-board A 8 tokens
- Command bob-statusline B 16 tokens
- Agent bob-foreman A 50 tokens
- MCP server bob-tasks A not measured
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 Changed a722b7899671
- 1mo ago First seen · 11 lines scan A 752c2ba3fbba
bob-companion is a plugin published in the GitHub repository PounceAI/bob-control (1 stars, last pushed 1mo ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
woterclip
GitHub Issues-backed agent orchestration with persona-based task routing for Claude Code.
software-factory
Lanes, tickets, and a human merge. Same skills as Cursor, Grok, and Codex.
vibe-flow
Orchestration skills for Vibe Kanban: plan → ship → link → review → merge with wave-based dispatch, executor routing (T0-T4), and autonomous fix loops.
orchestrate
Decompose a large goal into a tree of parallel workers running in isolated git worktrees, collect typed handoffs, replan, repeat until terminal. Idiomatic Claude Code realization of Cursor /orchestrate.
claude-code-pm
Autonomous Project Manager for Claude Code. Orchestrates parallel worker sessions to execute Linear tasks through a structured lifecycle: fetch, assign, implement, verify, review, merge.
on-the-record
The orchestration loop for contract v3: draft issues from the user's words, spawn role sessions (core plugins + role rulebook, agent account, issue- / branch), explain the PRs that come back, and relay the user's decisions — comments, review Approve, merge — with the user's own account, per conversation.