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/oborchers/fractional-ctoWrote 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/oborchers/fractional-cto/planning-tools)<a href="https://agentmods.dev/plugins/oborchers/fractional-cto/planning-tools"><img src="https://agentmods.dev/badge/plugins/oborchers/fractional-cto/planning-tools/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/oborchers/fractional-cto/planning-tools"><img src="https://agentmods.dev/badge/plugins/oborchers/fractional-cto/planning-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
planning-tools 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 5d 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": "planning-tools",
"version": "0.9.0",
"description": "Manage Claude Code's plan-mode artifacts, author multi-phase master planning documents, walk through open questions from any source (master plan, scope report, or the conversation itself), and synthesize dense progress entries to markdown / Linear / GitHub. Provides /plan-context (pre-load with optional ticket fetch), /plan-master (draft with optional ticket fetch), /plan-open-questions (interactive walkthrough with a 4-rung source ladder and source-aware apply), /plan-verify (audit), /plan-tick (auto-tick provenly-achieved phases), /plan-progress (per-branch progress entry with SHA-based idempotency), and /plan-delete (per-session cleanup). Integer-only phases, no sizing, plain-language chat output, every ticket and ADR named not just numbered, project-agnostic.",
"author": {
"name": "Dr. Oliver Borchers"
},
"repository": "https://github.com/oborchers/fractional-cto",
"license": "MIT",
"keywords": [
"plan-mode",
"planning",
"master-plan",
"multi-phase",
"verify-plan",
"tick",
"auto-tick",
"progress",
"linear",
"github",
"ticket-aware",
"open-questions",
"interactive-walkthrough",
"plain-language",
"cleanup",
"workflow",
"claude-code"
]
}
What it installs
The manifest is a name and a version. 5 skills, 7 commands, 3 agents travel with it, and installing the plugin installs all of them — 2,284 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill master-plan-methodology A 270 tokens
- Skill using-planning-tools A 244 tokens
- Skill plan-verification-checklist A 235 tokens
- Skill progress-methodology A 122 tokens
- Skill plain-language A 168 tokens
- Command plan-open-questions A 114 tokens
- Command plan-progress A 47 tokens
- Command plan-context A 35 tokens
- Command plan-tick A 56 tokens
- Command plan-verify A 34 tokens
- Command plan-master A 44 tokens
- Command plan-delete B 27 tokens
- Agent plan-master-architect A 266 tokens
- Agent plan-context-worker A 384 tokens
- Agent plan-verifier A 238 tokens
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.
- 5d ago First seen · 30 lines scan A 91d002253f06
planning-tools is a plugin published in the GitHub repository oborchers/fractional-cto (32 stars, last pushed 5d ago), licensed MIT. 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-10-13.
Other plugins, from other repositories
before-you-build
Pre-build product risk review for founders, product teams, and AI-assisted builders before implementation starts.
obw
Obsidian Workspace — project-scoped vault productivity (capture / notes / PM). Skills own folder layout and templates; /obw:pm splits a spec into blocking tickets; /issue is a Claude Mod pane that lists a view of the project's dashboard, draws Mermaid as text diagrams, and can open a card in the browser through viz.…
feature-to-pr-factory
Turn one feature into dependency-ordered GitHub or GitLab issues, then build each ticket into its own reviewed, tested PR or MR with agents.
mission-control
SDLC management for Operations, Asgard, and CAMPPS: prepared issue drafts, live schema sync, board schemas, labels, project fields, metrics, and card validation.
feishu-calendar
Manage Feishu (Lark) calendar events — create, read, update, delete events and manage attendees via the Feishu Open Platform Calendar API v4.
gse
GSE-One — AI engineering companion for structured SDLC management. 24 commands, adaptive risk analysis, unified backlog, knowledge transfer, worktree isolation.