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-161-automation-layering-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-161-automation-layering-strategy-audit)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-161-automation-layering-strategy-audit"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-161-automation-layering-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-161-automation-layering-strategy-audit"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-161-automation-layering-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.00030 | $0.00665 |
| 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-161-automation-layering-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 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 161: Automation Layering Strategy Audit
Purpose
Assess whether Google automation (Smart Bidding, PMax, broad match) is supplemented with appropriate guardrails. Pure automation without oversight leads to runaway spend, missed opportunities, or gradual performance drift. Layered control provides the best balance of AI efficiency and strategic governance.
Data Requirements
Data Source: Standard + Account Configuration Review
Standard Data:
data/account/campaigns/*/campaign.md- Bid strategies, automation settingsdata/account/bidding_strategies.md- Portfolio strategies
Additional Review Required:
- Automated rules configuration (Google Ads UI)
- Scripts deployed in account
- Third-party tools connected
- Review/monitoring cadence documentation
Reference GAQL:
SELECT
campaign.name,
campaign.bidding_strategy_type,
campaign.status
FROM campaign
WHERE campaign.status = 'ENABLED'
Use /google-ads:get-custom if you need to check specific automation configurations.
Analysis Steps
- Inventory automation: Document Smart Bidding strategies, PMax campaigns, broad match usage
- Evaluate guardrail coverage: Check for budget pacing rules, spend anomaly alerts, auto-pause rules
- Assess script coverage: Identify deployed scripts (budget pacing, n-gram analysis, anomaly detection)
- Review monitoring frequency: Verify alert configuration, dashboard review schedule, escalation procedures
- Identify conflicts: Check for competing automation or over-automation issues
Thresholds
| Condition | Severity |
|---|---|
| Smart Bidding with no budget protection rules | Critical |
| No anomaly detection (spend spike/drop alerts) | Critical |
| No script for search term/n-gram automation | Warning |
| Automated rules not running (check execution logs) | Warning |
| Weekly human review not documented | Warning |
| Scripts duplicating functionality | Info |
Output
Short format (default):
## Automation Layering Audit
**Account:** [Name] | **Automation coverage:** [X]% | **Guardrail gaps:** [Y]
### Critical ([Count])
- **Budget protection**: No rules configured -> Add spend alert at 80% daily budget
- **Anomaly detection**: Missing -> Configure CPA spike alerts
### Warnings ([Count])
- **Search term automation**: No n-gram script -> Deploy to catch waste between reviews
### Automation Inventory
| Layer | Coverage | Status |
|-------|----------|--------|
| Google Auto | X% | Good/Needs work |
| Rules/Alerts | X% | Good/Needs work |
| Scripts | X% | Good/Needs work |
| Human Review | X% | Good/Needs work |
### Recommendations
1. Deploy [script/rule] for [purpose]
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 · 86 lines · 30 tokens per session scan A 3e2ddd428bf0
skill-161-automation-layering-strategy-audit 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 665 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…