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 benyki/gtm-engine --skill engine-seogit clone --depth 1 https://github.com/benyki/gtm-engineWrote 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/benyki/gtm-engine/engine-seo)<a href="https://agentmods.dev/skills/benyki/gtm-engine/engine-seo"><img src="https://agentmods.dev/badge/skills/benyki/gtm-engine/engine-seo/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/benyki/gtm-engine/engine-seo"><img src="https://agentmods.dev/badge/skills/benyki/gtm-engine/engine-seo.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.00082 | $0.02665 |
| Opus 5.5 | $0.00033 | $0.01066 |
| Sonnet 5.5 | $0.00016 | $0.00533 |
| Haiku 4.5 | $0.00008 | $0.00266 |
Grade A, and why
engine-seo scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
description, canonical, OG/Twitter, JSON-LD, sitemap, RSS), and the curl checks How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
engine-seo
Finds a question people actually asked, answers it better than what currently ranks, and writes the piece in the user's voice.
This skill runs any engine folder of type seo. The default folder is
seo/; paths below (sources.json, inputs/, templates/, runs/, site/)
are inside that folder, while brand, accounts and keys live in shared/.
Two seo engines are fine — e.g. seo/ for the product blog and
seo-docs/ for a docs/comparison site, each with its own sources, site and
metric — scaffold with --merge --engine seo-docs:seo, or copy a folder
and empty its runs/ and reports/ (history belongs to the original).
Output is markdown, generated locally. Where it goes depends on whether they already have a site — see Publishing below. Either way nothing goes live without them saying so.
How (not just what):
| Step | Reference |
|---|---|
| Reddit / SERPs in the browser | references/browser-research.md |
| Find and validate subjects | references/subject-finding.md |
| Cut AI slop / keep voice — every draft, every run | references/anti-slop-writing.md |
| Publishing: the gate, metadata, deploy | references/publishing-site.md |
| After publish (Clarity → rewrites) | references/clarity-rewrite.md |
| Static site / CMS tradeoffs | references/advanced.md |
Paths in this file: shared/… means the gtm home (~/gtm by default, or
$GTM_HOME); templates/, inputs/, runs/ and reports/ mean the engine
folder you're running, wherever it lives. The scripts resolve both through
~/gtm/engines.json, so read them as names rather than literal paths.
Where topics come from
Read this engine's sources.json. The default is Reddit, and it needs no account.
Topics don't get found one at a time at the start of a writing run — that's how
you end up writing whatever you thought of that morning.
references/subject-finding.md is the weekly pass that mines the query grid,
validates against live SERPs, scores each candidate and kills the weak ones.
Its output is inputs/backlog.csv, and the bar is ≥20 rows at
status=validated at all times. Below that, top it up before writing
anything — the sources below are the raw material it draws on.
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.
- 1mo ago Changed d847288aded6
- 2mo ago First seen · 198 lines · 82 tokens per session scan A 7d771fa8728f
engine-seo is a skill published in the GitHub repository benyki/gtm-engine (4 stars, last pushed 6d ago), licensed MIT. It adds 82 tokens to every session and 2,665 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
engine-seo compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| engine-seobenyki/gtm-engine | Skill | 4 | 6d ago | MIT | A | 82 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | today | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | today | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 314k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |