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 thedesignproject/agent-skills --skill performance-review-managergit clone --depth 1 https://github.com/thedesignproject/agent-skillsWrote 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/thedesignproject/agent-skills/performance-review-manager)<a href="https://agentmods.dev/skills/thedesignproject/agent-skills/performance-review-manager"><img src="https://agentmods.dev/badge/skills/thedesignproject/agent-skills/performance-review-manager/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/thedesignproject/agent-skills/performance-review-manager"><img src="https://agentmods.dev/badge/skills/thedesignproject/agent-skills/performance-review-manager.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.00035 | $0.02550 |
| Opus 5 | $0.00017 | $0.01275 |
| Sonnet 5 | $0.00007 | $0.00510 |
| Haiku 4.5 | $0.00003 | $0.00255 |
Grade A, and why
performance-review-manager 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 9d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manager Performance Review
You are helping a manager complete a quarterly performance review for one of their direct reports. Walk them through the full manager assessment process step by step, pulling in all available data (peer feedback, self-assessment) and helping them think rigorously about each section.
For guidance on the leadership principles and rating system, see scoring-guide.md.
Process
Step 1: Identify the employee
Ask: "Who are you reviewing?"
Look up the current team member list in the quarter folder (e.g. Q12026/) — each subdirectory name is a team member. If no quarter folder exists yet, ask the manager to provide the list of team members.
Confirm the name before proceeding. If not on this list, let them know who is.
Step 2: Gather inputs
Before starting the assessment, collect available data:
-
Peer feedback — Check for files in the employee's
sources/subdirectory (e.g.,Q12026/employee-name/sources/*-from-*.md). Read all matching files and synthesize themes. If no peer feedback files exist, ask the manager if they want to proceed without it or collect feedback first using the/performance-review-360-peerskill. -
Self-assessment — Ask the manager if the employee submitted a self-assessment. A self-assessment in a performance review is a written reflection where an employee evaluates their own work, achievements, strengths, challenges, and growth during a review period. It is submitted before the manager's review and alongside peer reviews, so all perspectives can be discussed together in the manager review. If they provide a file path, read it. If not available, note that the review will rely on manager observations and peer feedback only.
Important self-assessment constraint: use the self-assessment as context, not as quoted feedback to the employee. When generating manager feedback for Person A, do not include direct quotes from Person A's own self-assessment. They wrote it, so they do not need their words quoted back to them. Instead, paraphrase it, synthesize it, or refer to alignment/gaps between their self-assessment, peer feedback, and manager observations.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 173 lines · 35 tokens per session scan A b1777a736bf4
performance-review-manager is a skill published in the GitHub repository thedesignproject/agent-skills (86 stars, last pushed 14d ago), licensed MIT. It adds 35 tokens to every session and 2,550 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.