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 LaGrowthMachine/gtm-system --skill sales-nav-search-buildergit clone --depth 1 https://github.com/LaGrowthMachine/gtm-systemWrote 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/lagrowthmachine/gtm-system/sales-nav-search-builder)<a href="https://agentmods.dev/skills/lagrowthmachine/gtm-system/sales-nav-search-builder"><img src="https://agentmods.dev/badge/skills/lagrowthmachine/gtm-system/sales-nav-search-builder/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/lagrowthmachine/gtm-system/sales-nav-search-builder"><img src="https://agentmods.dev/badge/skills/lagrowthmachine/gtm-system/sales-nav-search-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 68 Subtle instructions detected that may alter agent decision-making or introduce hidden biases.Fix: Review content for implicit steering or bias. Ensure instructions are explicit and align with the skill's stated purpose.
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.00221 | $0.06584 |
| Opus 5 | $0.00111 | $0.03292 |
| Sonnet 5 | $0.00044 | $0.01317 |
| Haiku 4.5 | $0.00022 | $0.00658 |
Grade A, and why
sales-nav-search-builder 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 11d 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 — 493 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sales Nav Search Builder
Converts a natural-language ICP description into a ready-to-click LinkedIn Sales Navigator search URL, including boolean strings for the title and keyword fields. Maintained by La Growth Machine.
Authority — read this first
This file is the canonical reference for everything you need to build a Sales Nav URL. The inline tables, presets, and rules below are exhaustive for common B2B targeting. The files in references/ exist for the long tail.
You do NOT need to consult these files — they're already inlined here:
references/spec-schema.md→ full spec format is belowreferences/boolean-search.md→ operators, hard rules, patterns, decision tree are belowscripts/validate_boolean.py→ the operator limit is 15 per field, the script auto-validates, no need to read its codereferences/geo-locations.md→ not needed for queries (only for extending regions.json)
The visual handoff (widget HTML + post-click decision tree) is inlined at the bottom of this file — no separate file to consult.
Consult references/industries.json ONLY when the user names an industry that's not in the top-10 table or in an industry preset below (e.g., "semiconductor manufacturing", "maritime shipping", "veterinary services").
Consult references/regions.json ONLY when the user names a country that's not in the top-30 table or in a region preset below (e.g., "Kazakhstan", "Senegal", "Trinidad").
If you find yourself running a grep or bash script to find an industry or region ID, stop — check the presets section first. The presets are designed to cover the way B2B sellers actually think about geography ("EMEA", "DACH", "Nordics") and verticals ("SaaS", "FinTech", "HRTech").
Workflow
- Build a JSON spec using the inline content below.
- Pipe the spec to the builder via stdin and capture the URL:
echo '<JSON_SPEC>' | python3 scripts/build_url.py - - Output the visual handoff — a brief framing line followed by
visualize:show_widget. See "Output format" at the end of this file. This step is mandatory and replaces any text-based summary. Do not paste the URL or explain segmentation choices in prose.
What ships with it
19 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.
- examples/founders-startups.json 986 B
- examples/marketing-leaders.json 1.2 KB
- examples/recent-job-changers.json 1.1 KB
- examples/sales-revops.json 1.6 KB
- README.md 5.7 KB
- references/boolean-search.md 6.7 KB
- references/company-headcount.json 392 B
- references/company-type.json 395 B
- references/functions.json 1.3 KB
- references/geo-locations.md 2.6 KB
- references/grammar.md 5.8 KB
- references/industries.json 29 KB
- references/languages.json 953 B
- references/regions.json 18 KB
- references/seniority.json 468 B
- references/spec-schema.md 2.6 KB
- references/years-ranges.json 239 B
- scripts/build_url.py 17 KB runs code
- scripts/validate_boolean.py 9.0 KB runs code
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.
- 11d ago First seen · 493 lines · 221 tokens per session scan A f1d5e97c3aae
sales-nav-search-builder is a skill published in the GitHub repository LaGrowthMachine/gtm-system (36 stars, last pushed 2d ago), licensed MIT. It adds 221 tokens to every session and 6,584 once invoked, about $0.0011 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.
Other skills, from other repositories
deepline-ads-audiences
Use this skill when building, enriching, auditing, or uploading B2B paid ads audiences to Google Customer Match, Meta/Facebook Custom Audiences, or LinkedIn Matched Audiences. Triggers on phrases like '/deepline-ads-audience', '/deepline-ads-audiences', 'upload this audience', 'create custom audiences', 'personal…
deepline-pre-research
Use when the user wants a last30days-style pre-research pass in Deepline: discover the critical public, private, CRM, workflow, social, and web data sources for a research/enrichment job; compare provider coverage; estimate Deepline credit cost; recommend the source plan before building or running the workflow; or…
niche-signal-discovery
Discover niche first-party signals that differentiate Closed Won vs Closed Lost accounts for ICP analysis. Use when the user provides won/lost customer domain lists and wants differential signals (website content, job listings, tech stack, maturity markers) to build account scoring models and prospecting criteria.…
deepline-engine
Build, publish, and verify a Deepline Play as a durable state machine over Customer DB tables, including a small paid pilot. Invoke this skill explicitly when the user asks to build an engine.
deepline-plays-review
Use this skill when a human needs to review a Deepline Play result and hand feedback, labels, or approval back to the agent for revision, evaluation, comparison, or bounded iteration. Triggers on “put this run in a Sheet,” “review these results,” “read my feedback,” “make this a standing rule,” “never regress on this…
deepline-plays
Use for Deepline GTM work that searches, enriches, scores, collects signals, or automates a workflow: find companies or people, enrich a CSV, find emails or LinkedIn, compare providers, build a waterfall, create a webhook or cron, or write a Play. For live information work, run a small heterogeneous experiment…