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/anthropics/knowledge-work-plugins/performance-reportnpx skills add anthropics/knowledge-work-plugins --skill performance-reportgit clone --depth 1 https://github.com/anthropics/knowledge-work-pluginsWrote 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/anthropics/knowledge-work-plugins/performance-report)<a href="https://agentmods.dev/skills/anthropics/knowledge-work-plugins/performance-report"><img src="https://agentmods.dev/badge/skills/anthropics/knowledge-work-plugins/performance-report.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.00058 | $0.04048 |
| Opus 5 | $0.00029 | $0.02024 |
| Sonnet 5 | $0.00012 | $0.00810 |
| Haiku 4.5 | $0.00006 | $0.00405 |
Grade A, and why
performance-report 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 yesterday.
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 — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance Report
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Generate a marketing performance report with key metrics, trend analysis, insights, and optimization recommendations.
Trigger
User runs /performance-report or asks for a marketing report, performance analysis, campaign results, or metrics summary.
Inputs
-
Report type — determine which type of report the user needs:
- Campaign report — performance of a specific campaign
- Channel report — performance across a specific channel (email, social, paid, SEO, etc.)
- Content performance — how content pieces are performing
- Overall marketing report — cross-channel summary (weekly, monthly, quarterly)
- Custom — user-defined scope
-
Time period — the reporting window (last week, last month, last quarter, custom date range)
-
Data source:
- If ~~marketing analytics is connected, discover what accounts and platforms are available, then pull performance data automatically
- If ~~product analytics is connected: pull performance data automatically
- If not connected: ask the user to provide metrics. Prompt with: "Please paste or share your performance data. I can work with spreadsheets, CSV data, dashboard screenshots described in text, or just the key numbers."
-
Comparison period (optional) — prior period or year-over-year for trend context
-
Stakeholder audience (optional) — who will read this report (executive summary style vs. detailed analyst view)
Report Structure
1. Executive Summary
- 2-3 sentence overview of performance in the period
- Headline metric with trend direction (up/down/flat vs. prior period)
- One key win and one area of concern
2. Key Metrics Dashboard
Present core metrics in a summary table:
| Metric | This Period | Prior Period | Change | Target | Status |
|---|
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.
- yesterday First seen · 393 lines · 58 tokens per session scan A 997397e23ba5
performance-report is a skill published in the GitHub repository anthropics/knowledge-work-plugins (23,849 stars, last pushed yesterday), licensed Apache-2.0. It adds 58 tokens to every session and 4,048 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…