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/trueclicks/claude-plugins/skill-026-rsa-description-optimizationnpx skills add TrueClicks/claude-plugins --skill skill-026-rsa-description-optimizationgit 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-026-rsa-description-optimization)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-026-rsa-description-optimization"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-026-rsa-description-optimization.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.1 | $0.00026 | $0.00595 |
| Opus 5 | $0.00013 | $0.00298 |
| Sonnet 5 | $0.00005 | $0.00119 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
skill-026-rsa-description-optimization 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 026: RSA Description Optimization
Purpose
RSAs support 4 descriptions but serve only 2 at a time. Having all 4 slots filled gives the algorithm more combinations to test and improves ad effectiveness. Unfilled description slots directly limit testing and typically result in lower Ad Strength ratings.
Data Requirements
Data Source: Standard
Standard Data:
data/account/campaigns/*/*/ads.md- RSA descriptions, headlines, ad strength
Reference GAQL:
SELECT
campaign.name,
ad_group.name,
ad_group_ad.ad.id,
ad_group_ad.ad.responsive_search_ad.descriptions,
ad_group_ad.ad_strength,
ad_group_ad.status,
metrics.impressions
FROM ad_group_ad
WHERE ad_group_ad.ad.type = 'RESPONSIVE_SEARCH_AD'
AND ad_group_ad.status != 'REMOVED'
AND segments.date DURING LAST_30_DAYS
Use /google-ads:get-custom for performance metrics by ad.
Analysis Steps
- Count descriptions per RSA: Min required 2, recommended 4, max 4
- Assess description quality: Character length utilization (80-90 char optimal), complete sentences
- Check diversity: Different angles in each description, avoid repetitive phrasing
- Identify missing elements: Benefits, CTAs, differentiators, social proof, offers
- Correlate with Ad Strength: Map description count to Ad Strength rating
Thresholds
| Condition | Severity |
|---|---|
| Descriptions = 2 | Warning |
| Descriptions = 3 | Info |
| Description < 40 characters | Warning |
| Duplicate descriptions | Critical |
| No CTA in any description | Warning |
Output
Short (default):
## RSA Description Audit
**Account:** [Name] | **RSAs:** [X] | **Issues:** [Y]
### Critical ([Count])
- **[Campaign] / [Ad Group]**: [X] descriptions, duplicates found -> Replace and add [Y] more
### Warnings ([Count])
- **[Campaign] / [Ad Group]**: [X] descriptions (need [Y] more)
### Summary
| Description Count | RSAs | % |
|-------------------|------|---|
| 4 | X | X% |
| 3 | X | X% |
| 2 | X | X% |
### Recommendations
1. [Priority action]
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 · 82 lines · 26 tokens per session scan A 2a575a40cd09
skill-026-rsa-description-optimization is a skill published in the GitHub repository TrueClicks/claude-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 595 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…