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 TrueClicks/claude-plugins --skill skill-152-historical-performance-benchmarking-seasonal-planninggit clone --depth 1 https://github.com/TrueClicks/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/skills/trueclicks/claude-plugins/skill-152-historical-performance-benchmarking-seasonal-planning)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-152-historical-performance-benchmarking-seasonal-planning"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-152-historical-performance-benchmarking-seasonal-planning/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/trueclicks/claude-plugins/skill-152-historical-performance-benchmarking-seasonal-planning"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-152-historical-performance-benchmarking-seasonal-planning.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.00030 | $0.00666 |
| Opus 5.5 | $0.00012 | $0.00266 |
| Sonnet 5.5 | $0.00006 | $0.00133 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
skill-152-historical-performance-benchmarking-seasonal-planning 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 21d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 152: Historical Performance Benchmarking for Seasonal Planning
Purpose
Pull and analyze prior-year performance data for seasonal periods to establish data-driven targets and budget recommendations. Historical benchmarking transforms seasonal planning from guesswork into informed strategy, preventing over- or under-investment during critical periods.
Data Requirements
Data Source: Custom GAQL Required
Standard 30-day export cannot provide prior-year comparisons. Need multi-year historical data for accurate benchmarking.
GAQL Query (Prior Year Seasonal Period):
SELECT
campaign.name,
campaign.advertising_channel_type,
segments.date,
metrics.impressions,
metrics.clicks,
metrics.cost_micros,
metrics.conversions,
metrics.conversions_value,
metrics.average_cpc
FROM campaign
WHERE campaign.status IN ('ENABLED', 'PAUSED')
AND segments.date BETWEEN '[PRIOR_YEAR_START]' AND '[PRIOR_YEAR_END]'
Run via /google-ads:get-custom for each seasonal period needing analysis (e.g., Black Friday 2025 to plan for 2026).
Analysis Steps
- Identify key seasonal periods: Map all major events requiring historical analysis
- Pull multi-year data: Query same periods across 2-3 years for trend analysis
- Calculate benchmarks: Compute volume metrics (impressions, clicks, conversions) and efficiency metrics (CTR, CPC, CPA, ROAS)
- Analyze trends: Identify growth rates, efficiency changes, and market shifts year-over-year
- Set targets: Establish realistic targets based on historical trends plus growth assumptions
Thresholds
| Condition | Severity |
|---|---|
| Major event planned without historical benchmark data | Critical |
| YoY efficiency decline >20% without acknowledged market shift | Warning |
| Budget target significantly higher than historical spend capacity | Warning |
| No multi-year comparison (single year data only) | Warning |
| Historical data unavailable (new account/campaign) | Info |
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.
- 21d ago First seen · 79 lines · 30 tokens per session scan A ead37075e8db
skill-152-historical-performance-benchmarking-seasonal-planning is a skill published in the GitHub repository TrueClicks/claude-plugins (2 stars, last pushed 22d ago), licensed MIT. It adds 30 tokens to every session and 666 once invoked, about $0.0001 per session on Opus 5.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-10-08.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…