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 skills add jeffreytse/grimoire-core --skill write-performance-reviewgit clone --depth 1 https://github.com/jeffreytse/grimoire-coreWrote 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/jeffreytse/grimoire-core/write-performance-review)<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/write-performance-review"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/write-performance-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/jeffreytse/grimoire-core/write-performance-review"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/write-performance-review.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00020 | $0.00939 |
| Opus 5 | $0.00010 | $0.00469 |
| Sonnet 5 | $0.00004 | $0.00188 |
| Haiku 4.5 | $0.00002 | $0.00094 |
Grade A, and why
write-performance-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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Performance Review
Write a performance review that is honest, specific, and developmentally useful — not a vague summary or a surprise.
Why This Is Best Practice
Adopted by: Adobe (replaced annual reviews with Check-ins), Microsoft (growth mindset reviews), Center for Creative Leadership SBI model used by 750K+ managers Impact: Adobe eliminated annual reviews in 2012 and saw voluntary turnover drop 30% while performance accountability increased; vague reviews correlate with higher attrition than no reviews
Why best: A performance review fails when it is too vague to act on or contains surprises the employee was never given a chance to address. The best reviews summarize feedback already delivered, add calibration context, and set a direction for growth.
Steps
- Gather evidence first — Pull 1:1 notes, project outcomes, peer feedback, and work artifacts from the entire review period. Do not write from memory alone.
- Rate against the role scorecard — Score each competency against the defined expectations for the level, not against peers. Calibration against peers happens in the calibration meeting, not in your written draft.
- Write accomplishments with impact — For each major contribution, use the format: "Did [action] → resulted in [measurable outcome]." Avoid adjectives without evidence ("great collaborator").
- Write development areas using SBI — Situation, Behavior, Impact. Be specific about what happened, not character traits. "In Q3 planning [S], estimates were regularly off by 50%+ [B], causing sprint commitments to slip 3 times [I]."
- Connect to career path — Name the one or two capabilities that, if developed, would most accelerate the person's next step. Make this concrete: "Presenting to the executive team without prep notes" not "improve communication."
- Check for bias — Re-read the review and ask: Would I write this same feedback for a different demographic? Replace "aggressive" with specific behavior. Replace "cultural fit" with a competency.
- Deliver before submitting to HR — Read the review together in the meeting. Give the direct report time to respond and add their own notes. Never submit and then inform.
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 · 54 lines · 20 tokens per session scan A 233bc07a4602
write-performance-review is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 20d ago), licensed MIT. It adds 20 tokens to every session and 939 once invoked, about $0.0001 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.
Other skills, from other repositories
org-report
Generate an executive organization brief (leadership chain, direct reports, extended teams, and vendor partners) for a target person. Produces a Word + PDF report from a directory MCP source (WorkIQ is the reference implementation) and displays it in a Copilot canvas. Triggers on "generate org report for X", "build…
meeting-efficiency
Agenda design, time boxing, decision capture, async alternatives, and productive facilitation.
coaching-techniques
GROW model, active listening, developmental feedback, and team growth approaches.
stakeholder-management
Influence mapping, communication strategies, and expectation management for complex organizations.
business-analysis
Patterns for requirements elicitation, BRDs, process analysis, and stakeholder alignment.
scaffolding-generator
Pattern-aware code scaffolding that detects existing conventions and generates new components matching the codebase style. Use when asked to "scaffold a component", "generate boilerplate", "create a new module", "bootstrap a service", "add a new endpoint", "create a new controller", or "add a new feature module".…