playbook-google-site-search

playbook-google-site-search is a skill for Claude Code, Codex from growthenginenowoslawski/coldoutboundskills. It costs 105 tokens per session (5,670 once invoked), scanned A, original, MIT.

A workflow that checks a company's own website for a chosen word or phrase using a Google site search. It returns whether the phrase appears and can provide a page to support the result.

In plain words
What is it for?
It is for filtering companies whose websites mention a specific keyword and creating a supported personalization line. It is not for discovering an entirely new company list.
Why use it?
Many useful details, such as certifications, services, technologies, or locations, are not available in structured company databases. This makes it easier to check those details across an existing list of websites.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: positional $N argument.

Good fit It is for filtering companies whose websites mention a specific keyword and creating a supported personalization line. It is not for discovering an entirely new company list.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/growthenginenowoslawski/coldoutboundskills/playbook-google-site-search
Install

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.

Any agent
npx skills add growthenginenowoslawski/coldoutboundskills --skill playbook-google-site-search
Clone the repo
git clone --depth 1 https://github.com/growthenginenowoslawski/coldoutboundskills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for playbook-google-site-search

README.md
[![agentmods](https://agentmods.dev/badge/skills/growthenginenowoslawski/coldoutboundskills/playbook-google-site-search/github.svg)](https://agentmods.dev/skills/growthenginenowoslawski/coldoutboundskills/playbook-google-site-search)
Your own site
<a href="https://agentmods.dev/skills/growthenginenowoslawski/coldoutboundskills/playbook-google-site-search"><img src="https://agentmods.dev/badge/skills/growthenginenowoslawski/coldoutboundskills/playbook-google-site-search/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.

agentmods 80×15 button for playbook-google-site-search

Your own site · 80×15
<a href="https://agentmods.dev/skills/growthenginenowoslawski/coldoutboundskills/playbook-google-site-search"><img src="https://agentmods.dev/badge/skills/growthenginenowoslawski/coldoutboundskills/playbook-google-site-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 105 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,670 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00105 $0.05670
Opus 5 $0.00053 $0.02835
Sonnet 5 $0.00021 $0.01134
Haiku 4.5 $0.00011 $0.00567

Measured 13d ago against content hash fe6d6924a68e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

playbook-google-site-search 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 13d 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.

skills/playbooks/playbook-google-site-search/SKILL.md · 363 lines

How it starts

The opening of the file, as written. The whole thing — 363 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Playbook: Google site: Keyword Filter

All rules here are best practice, not law. Override any of them when the campaign calls for it; note the best practice once and move on.

Use when: a campaign needs to know whether each company's own website talks about a specific thing — a certification, a technology, a service line, a location, a program name — and no structured API sells that field.

Do not use when: you need to find companies you do not have yet; when the thing you want is a page rather than a phrase (playbook-pricing-page, playbook-case-study-page); or when a real filterable field already exists (funding stage, headcount, technology installed) — filter at the source and skip this entirely.

One-line output: site_keyword_line = "you hold SOC 2 Type II certification", rendering as Noticed you hold SOC 2 Type II certification.

1. Trigger and scope

You have a list of domains. Someone asks "which of these mention X on their website?"

It does two jobs at once, and you should know which one you are buying. As a filter it tells you which rows to keep — that half is reliable. As a personalization signal it gives you an evidence URL and a line — that half needs the confidence gate in §2, because a page can contain your keyword for reasons that have nothing to do with the company.

It does not prove a company lacks something. The index is incomplete and its results are not even stable between two identical calls a minute apart (measured). An empty result means "not found in the index today", never "this company does not do X".

The rule that defines this playbook: one keyword, one query

site:acme.com "chess". Never site:acme.com ("chess" OR "checkers" OR "board games").

Measured:

Query Precision
site:n8n.io "SOC 2" 10/10 results contained the phrase
the same domain with a 7-term OR chain 4/10
site:uschess.org "Brooklyn" 8/10 on target
the same with an OR chain 2/10, and it drifted to a chess house in New Orleans

Read the full file on GitHub · 363 lines

Files

What ships with it

2 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.

Changes

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.

  1. 13d ago First seen · 363 lines · 0 tokens per session scan A fe6d6924a68e

Subscribe to this mod's changes

playbook-google-site-search is a skill published in the GitHub repository growthenginenowoslawski/coldoutboundskills (702 stars, last pushed 25d ago), licensed MIT. It adds 105 tokens to every session and 5,670 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens