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-socialgit 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-social)<a href="https://agentmods.dev/skills/benyki/gtm-engine/engine-social"><img src="https://agentmods.dev/badge/skills/benyki/gtm-engine/engine-social.svg" alt="Measured on agentmods" 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.00116 | $0.05138 |
| Opus 5 | $0.00058 | $0.02569 |
| Sonnet 5 | $0.00023 | $0.01028 |
| Haiku 4.5 | $0.00012 | $0.00514 |
Grade A, and why
engine-social 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 8d 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 — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
engine-social
Short-form written posts for LinkedIn, X, Bluesky, and other text social
channels. Much shorter feedback loop than engine-seo — you learn what works
in weeks rather than months.
This skill stands alone. It shares ideas with engine-seo and repeats some
of them in its own words, on purpose: the two engines are validated against
different evidence (a feed versus a search result), they'll drift apart as each
learns, and neither should be able to break the other. Everything this engine
needs is in its references/. Don't reach into another skill's folder.
This skill runs any engine folder of type social. The default folder
is social/; paths below (inputs/, templates/, runs/) are inside that
folder, while brand, accounts and keys are in shared/. Feel free to run
several social engines — social/ and social-founder-brand/ with
different goals and metrics are two independent folders — scaffold with
--merge --engine social-founder-brand:social, or copy one and empty its
runs/ and reports/ (history belongs to the original). Channels stay platform-named (linkedin, x,
bluesky, …).
How (not just what):
| Step | Reference |
|---|---|
| Find and validate subjects | references/subject-finding.md |
| Platforms / threads in the browser | references/browser-research.md |
| Cut AI slop / keep voice — every batch, every run | references/anti-slop-writing.md |
| Pre-built post parts with variations (optional) | templates/blocks/README.md (in the home) |
| Pick an image, or edit one via an image API (optional) | references/images.md |
| Write a thread + post on X / LinkedIn (browser) | references/threads-and-x.md |
| Post on Bluesky (API) | references/bluesky-post.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.
What ships with it
7 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.
- 8d ago First seen · 376 lines · 116 tokens per session scan A 058764178476
engine-social is a skill published in the GitHub repository benyki/gtm-engine (5 stars, last pushed 1mo ago), licensed MIT. It adds 116 tokens to every session and 5,138 once invoked, about $0.0006 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…