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 commands/fergupa/claude_plugins/performance-reportgit clone --depth 1 https://github.com/fergupa/claude_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/commands/fergupa/claude_plugins/performance-report)<a href="https://agentmods.dev/commands/fergupa/claude_plugins/performance-report"><img src="https://agentmods.dev/badge/commands/fergupa/claude_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.00014 | $0.01160 |
| Opus 5 | $0.00007 | $0.00580 |
| Sonnet 5 | $0.00003 | $0.00232 |
| Haiku 4.5 | $0.00001 | $0.00116 |
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 — 164 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 ~~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 |
|---|
Status indicators:
- On track (meeting or exceeding target)
- At risk (below target but within acceptable range)
- Off track (significantly below target)
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 · 164 lines · 14 tokens per session scan A 657186c43203
performance-report is a command published in the GitHub repository fergupa/claude_plugins (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 1,160 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.