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/ad-superpowers/ad-superpowers-plugin/client-context-onboardingnpx skills add Ad-Superpowers/ad-superpowers-plugin --skill client-context-onboardinggit clone --depth 1 https://github.com/Ad-Superpowers/ad-superpowers-pluginWrote 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/ad-superpowers/ad-superpowers-plugin/client-context-onboarding)<a href="https://agentmods.dev/skills/ad-superpowers/ad-superpowers-plugin/client-context-onboarding"><img src="https://agentmods.dev/badge/skills/ad-superpowers/ad-superpowers-plugin/client-context-onboarding.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 | $0.00129 | $0.03290 |
| Opus 5 | $0.00064 | $0.01645 |
| Sonnet 5 | $0.00026 | $0.00658 |
| Haiku 4.5 | $0.00013 | $0.00329 |
Grade A, and why
client-context-onboarding 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Client Context Onboarding
Purpose
Get the user's whole client portfolio into context in one guided pass, so every
other Ad Superpowers tool becomes client-aware. The skill enumerates connected ad
accounts, groups them into logical clients, enriches each with research, distills
the result into the lean client-context schema, and writes each client as a
reviewable draft with clients_update.
The payoff: once a client carries linked_accounts, clients(action="get", account_id=...) resolves any ad account to its owning client, and reports,
budget pacing, and media-buying stop treating accounts as anonymous. This skill is
the on-ramp that makes that resolution possible.
This is not single-client tooling. One run can onboard the entire portfolio, while also working for a single new client.
When to Use This Skill
Invoke when the user wants to:
- Onboard clients: "onboard my clients", "set up client context", "get all my clients into context".
- Import accounts into clients: "group my connected accounts into clients", "turn my ad accounts into client profiles".
- Populate a profile: "set up budgets and goals for client X", "fill in client X's accounts and KPIs".
Do NOT use for:
- The app signup/onboarding UI wizard (dashboard work, out of scope).
- User-account onboarding emails (separate track).
- Single-platform campaign builds (use the platform-specific skills).
- The agency 30/60/90-day operational kickoff (use
client-onboarding-checklist).
Before You Begin (gating)
The clients and clients_update tools are gated. Check for these signals and
translate each into a clear explanation instead of looping on a raw error:
| Signal | Meaning | What to do |
|---|---|---|
clients/clients_update not available |
The clients feature is not turned on for this connector yet | Tell the user the feature is not active yet, and stop. Do not promise it. |
permission_denied: |
The organization is read-only (can_write is off) |
Reads and grouping still work. Explain that writing client profiles needs write access; offer to show the proposed profiles and have them enable write or do it in the dashboard. |
no_active_organization |
No active org on the request | Ask the user to switch to an organization they belong to, then retry. |
| inactive subscription / trial ended | The plan is not active | Explain the subscription is not active; the write phase cannot run until it is. |
limit_exceeded / service_degraded |
Tool-call quota or a degraded backend | Stop the bulk cleanly, report progress so far, and suggest resuming later. |
limit_reached |
The plan's client cap is hit | Handle per client during the write phase (see Idempotency). |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 253 lines · 129 tokens per session scan A 2f7092fa2a8a
client-context-onboarding is a skill published in the GitHub repository Ad-Superpowers/ad-superpowers-plugin (5 stars, last pushed 6d ago), licensed MIT. It adds 129 tokens to every session and 3,290 once invoked, about $0.0006 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
analytics
Growth analytics authority — GA4 event tracking, conversion funnels, attribution models, cohort analysis, A/B testing, Supabase analytics queries, and revenue reporting patterns.
attribution-scope
GA4 has three distinct attribution scopes. Using the wrong scope gives misleading results. Choose based on the question you are answering.
traffic-diagnosis
Systematically diagnose why traffic changed — spike, drop, or shift in mix. Follow these steps in order. Each step narrows the hypothesis.
bot-traffic-detection
Identify and exclude bot, scraper, and spam sessions from GA4 data.
analytics
Use when instrumenting product or web analytics — GA4/PostHog SDK wiring, event taxonomy, funnels, double-counted events, consent gating, PII scrubbing. NOT charting that data (that is dashboard), NOT choosing which metrics matter (that is kpi-framework), NOT experiment math (that is ab-testing), NOT cookie-policy…
_mureo-shared
Skill "_mureo-shared" from logly/mureo, covering mureo shared patterns, installation, setup, claude code (recommended) and manual configuration.