run-performance-improvement-plan

run-performance-improvement-plan is a skill for Claude Code from jeffreytse/grimoire-core. It costs 49 tokens per session (2,543 once invoked), scanned A, original, MIT.

A formal, time-limited plan for an employee whose performance has repeatedly fallen below role expectations after informal feedback.

In plain words
What is it for?
Use it to define measurable goals, hold regular check-ins, document progress, and decide whether the performance standard has been reached.
Why use it?
It makes the expected improvement, support, review dates, and possible outcomes clear to both the manager and employee.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the grimoire-business plugin — 145 skills shipped together

Good fit Use it to define measurable goals, hold regular check-ins, document progress, and decide whether the performance standard has been reached.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeffreytse/grimoire-core/run-performance-improvement-plan
Install

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.

Any agent
npx skills add jeffreytse/grimoire-core --skill run-performance-improvement-plan
Clone the repo
git clone --depth 1 https://github.com/jeffreytse/grimoire-core

Made for: Claude Code.

Or install grimoire-business, the plugin that ships this one along with the rest of its 145 skills.

Wrote 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.

agentmods badge for run-performance-improvement-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/run-performance-improvement-plan/github.svg)](https://agentmods.dev/skills/jeffreytse/grimoire-core/run-performance-improvement-plan)
Your own site
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/run-performance-improvement-plan"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/run-performance-improvement-plan/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.

agentmods 80×15 button for run-performance-improvement-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/run-performance-improvement-plan"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/run-performance-improvement-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,543 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.02543
Opus 5 $0.00024 $0.01272
Sonnet 5 $0.00010 $0.00509
Haiku 4.5 $0.00005 $0.00254

Measured 6d ago against content hash 5542be87c9bb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

run-performance-improvement-plan 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 6d 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.

skills/business/leadership/skills/run-performance-improvement-plan/SKILL.md · 164 lines

How it starts

The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Run Performance Improvement Plan

Manage a direct report's documented performance gap through a structured, time-bound PIP with clear goals, regular check-ins, and defined success criteria — so both parties know exactly what is expected and what happens if those expectations are not met.

Why This Is Best Practice

Adopted by: The PIP is the standard structured underperformance management tool across enterprise HR systems globally; SHRM's "Managing Employee Performance" knowledge center documents the PIP as the industry-standard mechanism between informal feedback and separation; it is used at Google, Microsoft, Amazon, and all major employers as a legally documented intermediate step; HRCI (HR Certification Institute) includes PIP design and execution as a core competency in the PHR and SPHR certifications Impact: When executed correctly — with clear goals, regular check-ins, and genuine support — studies by CIPD (2020) show approximately 40–50% of employees on PIPs reach the defined performance standard; the primary value of a formal PIP is not termination — it is clarity: many employees on PIPs are succeeding in the wrong role, and the structured clarity of a PIP either surfaces the correct path or creates a legally defensible and humane record if separation becomes necessary; skipping the PIP and proceeding directly to separation exposes the organization to wrongful termination claims in most jurisdictions Why best: Informal feedback alone (give-developmental-feedback) fails for chronic underperformance because it lacks documented timelines, specific measurable standards, and defined consequences; performance reviews document the problem but do not provide a structured remediation path; the PIP bridges the gap between "we've had the conversation" and "we've given this person a real, documented, structured opportunity to succeed"

Sources: SHRM "Performance Improvement Plans: What Managers Need to Know" (shrm.org); CIPD "Managing Performance" guidance (cipd.org, 2020); HRCI PHR Body of Knowledge; Littler Mendelson "Termination Best Practices" (littler.com); Harvard Business Review "The Right Way to Use a PIP" (2016)

Read the full file on GitHub · 164 lines

Changes

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.

  1. 6d ago First seen · 164 lines · 49 tokens per session scan A 5542be87c9bb

Subscribe to this mod's changes

run-performance-improvement-plan is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 21d ago), licensed MIT. It adds 49 tokens to every session and 2,543 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-09-03.