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-131-change-history-monitoringgit 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-131-change-history-monitoring)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-131-change-history-monitoring"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-131-change-history-monitoring/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-131-change-history-monitoring"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-131-change-history-monitoring.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.00027 | $0.00617 |
| Opus 5.5 | $0.00011 | $0.00247 |
| Sonnet 5.5 | $0.00005 | $0.00123 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
skill-131-change-history-monitoring 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 131: Change History Monitoring
Purpose
Monitor all account changes to identify who made what changes, track auto-applied recommendations, and flag unusual activity. Essential for accountability, troubleshooting performance shifts, and maintaining control over account automation.
Data Requirements
Data Source: Custom GAQL Required
Change history data requires the change_event resource which is not in standard exports.
GAQL Query:
SELECT
change_event.change_date_time,
change_event.change_resource_type,
change_event.resource_change_operation,
change_event.changed_fields,
change_event.client_type,
change_event.user_email
FROM change_event
WHERE change_event.change_date_time DURING LAST_14_DAYS
LIMIT 1000
Run via /google-ads:get-custom with query name change_history.
Analysis Steps
- Fetch change history: Run GAQL query for recent account changes
- Categorize by source: Group changes by user, API, automated rules, Google internal
- Identify critical changes: Flag budget, bidding, and status changes
- Track auto-applied changes: Filter for
GOOGLE_ADS_RECOMMENDATIONS_SUBSCRIPTION(auto-applied) andGOOGLE_ADS_RECOMMENDATIONS(manually accepted) - Detect anomalies: Flag unusual volumes or off-hours activity
Thresholds
| Condition | Severity |
|---|---|
| Budget change without documentation | Critical |
| Bidding strategy changed unexpectedly | Critical |
| Auto-applied changes not reviewed | Warning |
| >50 changes in 1 hour (unusual volume) | Warning |
| Changes from unknown API source | Info |
Output
Short format (default):
## Change History Audit
**Account:** [Name] | **Period:** Last 14 days | **Total Changes:** [X]
### Change Summary by Source
| Source | Changes |
|--------|---------|
| Manual (UI) | [X] |
| Automated Rules | [X] |
| Auto-Applied (Google) | [X] |
| API/Scripts | [X] |
### Critical Changes to Review
- **[Date]**: Budget changed from $[X] to $[Y] by [User]
- **[Date]**: Bidding strategy changed on [Campaign] by [User]
### Auto-Applied Changes
- [X] recommendations auto-applied → Review for appropriateness
### Anomalies Detected
- **[Date]**: [X] changes in 1 hour from [Source]
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 · 83 lines · 27 tokens per session scan A 3406de6263fb
skill-131-change-history-monitoring is a skill published in the GitHub repository TrueClicks/claude-plugins (2 stars, last pushed 22d ago), licensed MIT. It adds 27 tokens to every session and 617 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…