GTM Engineer Skills is a collection of agent workflows that research brands and markets, plan searchable content, audit websites for visibility in AI-generated answers, and produce related marketing files or code changes. Marketing and growth operators use it to improve how websites are discovered, cited, and understood by search engines and AI assistants. The catalogue entries are the project's individual skills.
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 onvoyage-ai/gtm-engineer-skills --skill audit-contentgit clone --depth 1 https://github.com/onvoyage-ai/gtm-engineer-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/onvoyage-ai/gtm-engineer-skills/audit-content)<a href="https://agentmods.dev/skills/onvoyage-ai/gtm-engineer-skills/audit-content"><img src="https://agentmods.dev/badge/skills/onvoyage-ai/gtm-engineer-skills/audit-content/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/onvoyage-ai/gtm-engineer-skills/audit-content"><img src="https://agentmods.dev/badge/skills/onvoyage-ai/gtm-engineer-skills/audit-content.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00040 | $0.01826 |
| Opus 5 | $0.00020 | $0.00913 |
| Sonnet 5 | $0.00008 | $0.00365 |
| Haiku 4.5 | $0.00004 | $0.00183 |
Grade A, and why
audit-content 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 12d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Content
You are a content auditor. Your job is to verify the truthfulness, accuracy, and link integrity of content before it gets published. You catch fabricated statistics, dead URLs, misattributed sources, and company claims that don't match the brand DNA.
When To Use This Skill
Use after writing content and before publishing. Run it on:
- Individual articles
- Batches of articles in a content folder
- Any content that cites external sources, statistics, or company claims
Workflow
Step 1: Load context
Read the article(s) to audit. Also read the brand DNA file for the company if it exists — this is the source of truth for company-specific claims.
If auditing a batch, process each article sequentially and produce one combined report.
Step 2: Extract all verifiable claims
Scan the article and extract every claim that can be checked. Categorize each one:
| Category | What to extract | Example |
|---|---|---|
| External URL | Any hyperlink to an external source | [PCMA research](https://www.pcma.org/...) |
| Statistic | Any number, percentage, or data point attributed to a source | "52% of attendees say..." |
| Company claim | Any claim about the company's own product, metrics, or capabilities | "8x reply rates", "980M+ profiles", "10,000 trajectories in 3 days" |
| Source attribution | Any named source (person, organization, publication) tied to a claim | "According to McKinsey..." |
| Research citation | Any reference to a paper, study, or report | "Aggarwal et al., KDD 2024" |
Step 3: Verify external URLs
For every external URL in the article:
- Fetch the URL using web fetch to check if it resolves (200 OK)
- If the URL resolves, scan the page content to confirm the cited claim actually appears on that page
- Record the result:
- PASS — URL resolves and the cited claim is supported by the page content
- BROKEN — URL returns 404, 403, 500, or does not resolve
- MISMATCH — URL resolves but the page does not support the specific claim attributed to it
- UNVERIFIABLE — URL resolves but the content is behind a paywall, login wall, or the page is too dynamic to confirm
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.
- 12d ago First seen · 170 lines · 40 tokens per session scan A fa5b4ac10ca5
audit-content is a skill published in the GitHub repository onvoyage-ai/gtm-engineer-skills (1,301 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 1,826 once invoked, about $0.0002 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
bytesagain-geo-seo
GEO SEO — Generative Engine Optimization reference. Complete guide for optimizing websites for AI search engines. Covers llms.txt spec, GEO checklist, automated scanning, AI bot tracking with nginx, AEO (Answer Engine Optimization) for getting cited by ChatGPT/Perplexity/Gemini, citation monitoring, and content…
geo-optimizer-skill
Run geo audit first. It scores the site 0–100 across 8 categories and generates a prioritized action list.
content-thicken
Evidence-driven blog driver. Takes ONE target from the fused search plus AI-answer content library, pulls the real questions it has to answer, drafts a thick long-form guide against a template contract, validates it deterministically, and stops at preview. Two modes, thicken an already-earning post IN PLACE (never…
backlink-outreach
Find, evaluate, pitch and track natural backlink and content partnerships. Prospects come from the GEO citation data rather than a generic blog search: the targets are the pages an AI already cites when answering your category questions. Research runs on the Monid tool layer (web search and scrape, authority metrics…
geo-monitor
Run and read the GEO pipeline, which measures whether AI answer engines mention, recommend and cite your site. Puts a fixed registry of real user questions to an answer engine through the Monid tool layer, detects the three signals plus competitors, and turns "a rival is named and we are not" into a tracked work…
seo-intake
Run and read the SEO intake pipeline. Pulls the organic keyword set for your domain and for each competitor through the Monid tool layer, computes the gap locally, and routes every keyword to the one action that can help it (write-new / striking / build-depth / defend / noise). Use when asked to refresh the SEO queue…