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 google-feed-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/google-feed-ops)<a href="https://agentmods.dev/skills/sergeyizmailov/knowledge-delta-skills/google-feed-ops"><img src="https://agentmods.dev/badge/skills/sergeyizmailov/knowledge-delta-skills/google-feed-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/google-feed-ops"><img src="https://agentmods.dev/badge/skills/sergeyizmailov/knowledge-delta-skills/google-feed-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.00166 | $0.01656 |
| Opus 5.5 | $0.00066 | $0.00662 |
| Sonnet 5.5 | $0.00033 | $0.00331 |
| Haiku 4.5 | $0.00017 | $0.00166 |
Grade A, and why
google-feed-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 1mo 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Feed Ops
Reviewed 2026-09-02. Baseline: Sonnet 5 / Claude Code subagent / 2026-09-02; 2026-09-03 blind suspension task [R] — site-review and second-account rules already known. The retail data layer. Google Ads buys the traffic; the feed decides what is eligible, what it costs, and what gets suspended — and the Merchant Center account is reviewed on the site, not the feed. No Facebook analogue at this depth.
Route: buy mechanics → google-ads · infra/survival/agency accounts and MC↔Ads cascade →
google-grey-ops (12) · counting → tracker-ops · portfolio decisions → senior-buyer-ops.
Check first
| Need | Reference |
|---|---|
| New account → products serving, in order; first campaign on a fresh pair | references/04-gmc-launch-runbook.md |
Merchant API v1 facts, what the API cannot do, gmcops doctor gates |
references/05-merchant-api-ops.md |
| Attributes, limits, submission methods, titles, custom labels | references/01-feed-spec-and-submission.md |
| Suspensions, the gates that block review, required website elements, ratings | references/02-merchant-center-suspensions.md |
| Standard Shopping priority ladder, PMax retail structure, product-level reporting, CSS | references/03-shopping-pmax-retail.md |
gmcops lives in google-grey-ops/scripts/ (one uv project with googleops); usage in
google-grey-ops/10. Read-only doctor first: gmcops --account <id> --json doctor --country US.
Three things that break accounts
- The five review gates. Shipping settings · a data source for the target country · website URL claimed and verified · business address verified · US tax settings. Missing any one blocks review entirely. This is the real cause of most "products not showing" tickets — check before diagnosing anything else.
- Feed vs live page mismatch on price and availability. Google's automated crawl fires preemptive item disapproval. It is automated, so the fix is a sync fix, never an appeal-and-argue. Compare against the checkout total, not just the product page.
- Promotional text in titles or descriptions. A policy trigger, not a soft ranking issue.
What ships with it
5 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.
- 1mo ago Changed · +14 lines · +100 tokens per session 8b6cd51387b2
- 1mo ago First seen · 93 lines · 66 tokens per session scan A 0e9408c28d3e
google-feed-ops is a skill published in the GitHub repository sergeyizmailov/knowledge-delta-skills (3 stars, last pushed 1mo ago), licensed MIT. It adds 166 tokens to every session and 1,656 once invoked, about $0.0007 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-08-31.
Other skills, from other repositories
code-review
Use when asked to review a PR, MR, branch, or diff, audit changed files, or check code quality.
review-contract
Clause-by-clause contract review — inventories key clauses (term, termination, liability cap, indemnity, IP, payment, confidentiality, governing law, auto-renewal), flags deviations from market-standard positions with RED/YELLOW/GREEN severity and verbatim quotes, drafts redline language, and sets negotiation…
pr-review
Use when opening, reviewing, or merging a pull request. Covers pre-PR checks (linting, tests, branch naming), PR description requirements, and post-merge cleanup. Not for code review commentary or architecture decisions — use the relevant role guidelines for those.
thermo-nuclear-code-quality-review
Strict branch-diff review against the ticket spec. Use after a dev session, before a PR, or when the user asks to review the branch. execute-plan runs it as its review gate — do not also invoke it unless code changed after Verdict: ship.
review-build
Strict review of the branch diff against the ticket spec. implement-plan runs it as the review gate; invoke directly after a dev session or before a PR (sdlc-lite chain).
pn-dcf-model
Discounted cash flow valuation. Structure revenue and margin assumptions, build a free cash flow bridge, derive WACC, compute terminal value, and output an implied equity value range with sensitivity tables. Use standalone or as the second leg of a full valuation summary alongside pn-comps-analysis.