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-028-rsa-pinning-strategy-auditgit 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-028-rsa-pinning-strategy-audit)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-028-rsa-pinning-strategy-audit"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-028-rsa-pinning-strategy-audit/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-028-rsa-pinning-strategy-audit"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-028-rsa-pinning-strategy-audit.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.00026 | $0.00667 |
| Opus 5 | $0.00013 | $0.00333 |
| Sonnet 5 | $0.00005 | $0.00133 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
skill-028-rsa-pinning-strategy-audit 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 12d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 028: RSA Pinning Strategy Audit
Purpose
Pinning headlines or descriptions to specific positions restricts ad combinations Google can test. Strategic pinning (brand name to H1) is acceptable, but over-pinning (3+ pins) significantly reduces optimization ability and lowers Ad Strength.
Data Requirements
Data Source: Standard
Standard Data:
data/account/campaigns/*/*/ads.md- RSA headlines/descriptions with pinned positions
Reference GAQL:
SELECT
campaign.name,
ad_group.name,
ad_group_ad.ad.id,
ad_group_ad.ad.responsive_search_ad.headlines,
ad_group_ad.ad.responsive_search_ad.descriptions,
ad_group_ad.ad_strength,
ad_group_ad.status
FROM ad_group_ad
WHERE ad_group_ad.ad.type = 'RESPONSIVE_SEARCH_AD'
AND ad_group_ad.status != 'REMOVED'
Note: Headlines array includes pinned_field property (HEADLINE_1, HEADLINE_2, HEADLINE_3) or null.
Analysis Steps
- Count pinned assets per RSA: Total pinned headlines and descriptions
- Evaluate pinning impact: Calculate possible combinations reduction (>50% reduction is problematic)
- Assess pinning strategy: Brand H1 only (acceptable), H1+CTA (acceptable), 3+ headline pins (problematic), all positions pinned (defeats RSA purpose)
- Correlate with performance: Compare pinned vs unpinned RSA performance
- Flag conflicting pins: Multiple assets pinned to same position
Thresholds
| Condition | Severity |
|---|---|
| 5+ total pins | Critical |
| All H positions pinned (H1+H2+H3) | Critical |
| 3-4 total pins | Warning |
| Combination reduction >90% | Critical |
| 1-2 pins | Info |
Output
Short (default):
## RSA Pinning Audit
**Account:** [Name] | **RSAs:** [X] | **Over-pinned:** [Y]
### Critical ([Count])
- **[Campaign] / [Ad Group]**: [X] pins (H1:[a], H2:[b], H3:[c], D1:[d], D2:[e]) -> Remove [pins]
### Warnings ([Count])
- **[Campaign] / [Ad Group]**: [X] pins -> Consider removing [specific pins]
### Summary
| Pinning Level | RSAs | Avg Ad Strength |
|---------------|------|-----------------|
| None (0 pins) | X | [rating] |
| Light (1-2) | X | [rating] |
| Heavy (3+) | X | [rating] |
### 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.
- 12d ago First seen · 81 lines · 26 tokens per session scan A e5ff83f10976
skill-028-rsa-pinning-strategy-audit 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 667 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…
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…