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 agentmods add skills/jpicklyk/task-orchestrator/plugin-impact-reviewnpx skills add jpicklyk/task-orchestrator --skill plugin-impact-reviewgit clone --depth 1 https://github.com/jpicklyk/task-orchestratorWrote 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/jpicklyk/task-orchestrator/plugin-impact-review)<a href="https://agentmods.dev/skills/jpicklyk/task-orchestrator/plugin-impact-review"><img src="https://agentmods.dev/badge/skills/jpicklyk/task-orchestrator/plugin-impact-review.svg" alt="Measured on agentmods" 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 | $0.00046 | $0.00570 |
| Opus 5 | $0.00023 | $0.00285 |
| Sonnet 5 | $0.00009 | $0.00114 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
plugin-impact-review 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.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Impact Review Framework
Evaluate which plugin components need updating after changes to MCP tools, config format, or response shapes.
Step 1: Skill Impact
Search all skill files for references to the changed behavior:
grep -r "<tool-name>\|<config-key>\|<changed-concept>" claude-plugins/task-orchestrator/skills/
For each match:
- Does the skill reference the old behavior, field name, or response shape?
- Does the skill need updated instructions or examples?
- Are trigger phrases still accurate?
Step 2: Hook Impact
Search hook scripts for references:
grep -r "<tool-name>\|<changed-concept>" claude-plugins/task-orchestrator/hooks/
For each match:
- Does the hook inject context that references the old behavior?
- Does the hook read tool input/output fields that changed?
- Does the hook matcher still target the correct tool name?
Step 3: Config Format Documentation
Check claude-plugins/task-orchestrator/skills/manage-schemas/references/config-format.md:
- YAML structure example reflects current format
- Field reference table has all current fields
- Descriptions match current behavior
Step 4: Output Style References
Check output styles for stale references:
-
workflow-orchestrator.md— any references to changed tools, fields, or workflows - Zone 1 (shared core) vs Zone 2/3 (extensions) — changes in Zone 1 must be synced to
workflow-analyst.md
Step 5: Plugin Caching
- Are hook scripts changed? If yes,
/plugin marketplace remove+ re-add required (content cached) - Are skill files changed?
/reload-pluginssufficient (read at invocation) - Are output styles changed?
/reload-pluginssufficient
Output
Compose the plugin-impact note listing specific files and sections that need changes. Note /mcp reconnect requirements.
Before asserting any skill/hook/doc file is missing, verify with a direct existence check
(Read the exact expected path, or an exact-path Glob) — skills live in BOTH
claude-plugins/task-orchestrator/skills/ and project-level .claude/skills/; checking
only one directory has produced a false "missing skill" finding before.
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 · 64 lines · 46 tokens per session scan A 52278b608580
plugin-impact-review is a skill published in the GitHub repository jpicklyk/task-orchestrator (205 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 570 once invoked, about $0.0002 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-30.
Other skills, from other repositories
pneuma-project
Project-context awareness — multi-session workflows around one topic, shared materials and preferences, and cross-mode handoffs as a high-value user path.
vc-generate-phase-program
Generate kickoff artifacts for a multi-phase program: umbrella plan, Program Goal Charter, session-goal block, per-phase plan stubs, and the 7-step per-phase inner loop reference.
vc-intent-clarify
Clarify intent before RIPER-5 phase delegation. Scores ambiguity (4 signals); generates structured multi-choice questions for Tier 2. Two-mode: SIMPLE and DEEP.
vc-validate-findings
Use when running VALIDATE V2-V3 fan-out. Two-layer investigation (4 dimension agents + per-section feasibility agents) synthesized into PASS/CONDITIONAL/BLOCKED net gate. Strategy-agnostic.
vc-agent-browser
AI-optimized browser automation CLI with context-efficient snapshots. Use for long autonomous sessions, self-verifying workflows, video recording, and cloud browser testing (Browserbase).
vc-scenario
Generate comprehensive edge cases and test scenarios by decomposing features across 12 dimensions. Use before implementation or testing to catch issues early.