Borrowing it
Nothing to install: this file belongs to jpicklyk/task-orchestrator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jpicklyk/task-orchestrator/main/.claude/skills/plugin-impact-review/SKILL.mdgit 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/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/skills/jpicklyk/task-orchestrator/plugin-impact-review"><img src="https://agentmods.dev/badge/skills/jpicklyk/task-orchestrator/plugin-impact-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.00620 |
| Opus 5.5 | $0.00019 | $0.00248 |
| Sonnet 5.5 | $0.00009 | $0.00124 |
| Haiku 4.5 | $0.00005 | $0.00062 |
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 24d 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: Orchestration Context References
Check the orchestration context for stale references:
-
hooks/orchestration-context.mjs— any references to changed tools, fields, or workflows in the injected core (both theworkflowandschemavariants) -
skills/orchestrate/SKILL.md— tier table, delegation table, and phase-owner dispatch rules
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) - Is the orchestration-context hook content changed? Needs a session restart (or the forced cache refresh in
claude-plugins/CLAUDE.md), not/reload-plugins; theorchestrateskill is read at invocation
Output
Compose the plugin-impact note listing specific files and sections that need changes. Note /mcp reconnect requirements.
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.
- 24d ago Changed · +1 tokens per session 144cf16ea0e5
- 1mo 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 (210 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 620 once invoked, about $0.0002 per session on Opus 5.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
pinescript
Pine Script v6: syntax, performance, error diagnosis, backtesting, visualization. Use when writing or debugging .pine files or TradingView Pine indicators/strategies.
debugging
Systematic root-cause debugging with verification. Use for errors, stack traces, broken tests, flaky tests, regressions, or anything not working as expected. For validating bug reports before fixing, use bug-reproduction-validator agent.
document-review
Structural and accuracy review of documents: gaps, clarity, completeness, organization, and claims checked against the code. Use when a brainstorm, plan, spec, ADR, or any doc needs polish before the next workflow step. For exploring new ideas from scratch, use brainstorming instead.
reflect
Session retrospective and skill audit. Use when asked to reflect, do a retrospective, review lessons learned, audit what went well or wrong, or review session effectiveness.
c-systems
C patterns for systems code, libraries, and native extensions: module layout, function decomposition, status-enum errors, memory safety, undefined behavior, and performance measurement. Use when writing, reviewing, refactoring, or debugging C, working with malloc lifetimes, buffer overflows, sanitizers, or Valgrind…
cpp-systems
Modern C++ patterns: RAII and ownership, rule of zero/five, exceptions and error handling, API and ABI boundaries, templates, and CMake tooling. Use when writing, reviewing, refactoring, or debugging C++, working with smart pointers, move semantics, memory leaks, template errors, or gtest. For plain C, see…