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 sergeyizmailov/knowledge-delta-skills --skill senior-buyer-opsgit clone --depth 1 https://github.com/sergeyizmailov/knowledge-delta-skillsWrote 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/sergeyizmailov/knowledge-delta-skills/senior-buyer-ops)<a href="https://agentmods.dev/skills/sergeyizmailov/knowledge-delta-skills/senior-buyer-ops"><img src="https://agentmods.dev/badge/skills/sergeyizmailov/knowledge-delta-skills/senior-buyer-ops/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/sergeyizmailov/knowledge-delta-skills/senior-buyer-ops"><img src="https://agentmods.dev/badge/skills/sergeyizmailov/knowledge-delta-skills/senior-buyer-ops.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.00106 | $0.01036 |
| Opus 5 | $0.00053 | $0.00518 |
| Sonnet 5 | $0.00021 | $0.00207 |
| Haiku 4.5 | $0.00011 | $0.00104 |
Grade A, and why
senior-buyer-ops 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 8d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Senior Buyer Ops
The layer above the four adapters (buy / survive / count / measure): they tell you HOW; this tells you WHAT to decide as the person accountable for a portfolio and a team's numbers. Call the adapters in order; this file owns the decisions between them.
Route by platform, then by layer:
| Layer | Meta | |
|---|---|---|
| Buy mechanics | meta-ads |
google-ads |
| Infra / launch / survival | meta-grey-ops |
google-grey-ops |
| Retail data layer | — | google-feed-ops |
Scope: Meta (FB/IG) + Google Ads only — no Microsoft Ads, TikTok, or other networks.
Platform-agnostic: trackers/metrics → tracker-ops · is-a-result-real →
measurement-experimentation-ops · portfolio & cadence →
references/01-portfolio-and-cadence.md · creative production →
references/02-creative-ops.md · funnel QA → references/03-funnel-ops.md ·
automated kill/scale rules that survive small samples →
references/04-automated-rules.md · which automation pipe (API/MCP/CSV/Sheets)
for agent vs human → references/05-automation-channels.md · platform is Google → also read references/06-google-lane.md (contract additions, structure-doctrine rationale, channel detail).
Do not port structure doctrine between platforms — Google splits by intent and unit economics, not by campaign count; merging price tiers/funnel stages the way Meta rewards fails there (mechanics: references/06-google-lane.md).
Before you scale or kill on a difference, confirm it's real, not noise
(measurement-experimentation-ops): the kill/scale ladder and marginal-scaling
math below assume a MATURED, non-contaminated result.
Operating contract (pin on day 1, in writing — before any spend)
The single most expensive mistake is optimising against the wrong definition. Get these from the TL explicitly, don't infer:
- Payout event — WHICH tracker status/measure pays (lead? reg? FTD? qualified FTD? confirmed COD?). Everything downstream is priced on this.
- Downstream stages + conversion lag — how long until the payout event matures (call-center confirm / deposit / KYC). Sets your judging window.
- Caps — daily/total offer caps; traffic past a cap is unpaid.
- KPI + targets — target CPA/CPL, and the QUALITY metric the advertiser judges later (reg→FTD, confirm %, scrub rate).
- Timezone and currency of every ad account — the tz used for every daily
number and the sheet. Google serving-account tz/currency are permanent
(
google-grey-ops/07). Meta change closes the account and opens a new act ID (meta-grey-ops/08). A mismatch is overhead for the life of the seat. - Naming + mapping — the campaign-name convention and the Meta-macro→tracker- param mapping that makes it split (tracker-ops mapping contract).
- Reporting source of truth — which sheet/dashboard is authoritative and by when each day.
- Responsibility zones + escalation — who owns accounts/creatives/tracker/ payments; who to ping on a ban wave, a tracking break, a billing hold.
What ships with it
6 files 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.
- 8d ago Changed · -14 lines a0d01e33695b
- 12d ago First seen · 89 lines · 106 tokens per session scan A a9c388c2c1a7
senior-buyer-ops is a skill published in the GitHub repository sergeyizmailov/knowledge-delta-skills (3 stars, last pushed 4d ago), licensed MIT. It adds 106 tokens to every session and 1,036 once invoked, about $0.0005 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
react-testing
React component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress end-to-end runs. Use when writing or fixing tests for React components, hooks, or pages.
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
qa
QA test your code changes by reading your git diff, choosing the right validation path for frontend/browser and backend changes, and reporting pass/fail with evidence.
architecture-feature-first
Use when creating a feature, designing folder structure, adding repositories/services/view models, wiring dependency injection, or deciding which layer owns logic.
testing
Verify a Skyvern deployment is working correctly by smoke-testing the backend API, frontend rendering, browser session provisioning, and workflow execution. Use when the user says 'is Skyvern working', 'test my deployment', 'verify the installation', 'smoke test', or needs to check that a self-hosted or local Skyvern…