Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Jasper0122/agent-seo-kitnpx agentmods add skills/jasper0122/agent-seo-kit/content-thickenWrote 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/jasper0122/agent-seo-kit/content-thicken)<a href="https://agentmods.dev/skills/jasper0122/agent-seo-kit/content-thicken"><img src="https://agentmods.dev/badge/skills/jasper0122/agent-seo-kit/content-thicken.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.00126 | $0.03547 |
| Opus 5 | $0.00063 | $0.01774 |
| Sonnet 5 | $0.00025 | $0.00709 |
| Haiku 4.5 | $0.00013 | $0.00355 |
Grade A, and why
content-thicken 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 7d 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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content thicken
The single writing skill. Selection, brief, drafting and validation live here. Two things live outside it on purpose:
PRODUCT.md, which you write once. What your product actually is, what it cannot do, what you are not allowed to claim. See references/PRODUCT.template.md.TEMPLATE.md, the shape of an article on your blog. Start from references/article-template.md.
Splitting "how to write" from "what is true" across two files is how they drift into contradicting each other. One definition each, referenced from here.
The one rule that must never break
Two output modes. Picking the wrong one destroys traffic that already exists.
| Mode | When | The URL |
|---|---|---|
| In place | The post already earns clicks or holds a real ranking | Keep the exact slug, file name and route. Rewrite in place, add depth and figures. Never move it, never add a redirect, never touch its sitemap entry. |
| New guide | Net-new topic, or a page with no equity yet | A new URL is free here because there is nothing to protect. |
When unsure, thicken in place. Moving a URL that a search engine already sends traffic to is the one irreversible mistake this pipeline can make.
Non-negotiable inputs
Do not draft until each of these is known or explicitly marked a hypothesis:
primaryKeyword the verified query or question
questions the real questions this must answer, from questions-for.mjs
searchIntent informational | commercial | comparison | troubleshooting
demandEvidence an intake row, a gap row, a real thread, or a GEO attack word
productEvidence features that really exist, checked today, not from memory
conversionGoal the page it should send a reader to
internalLinks live URLs, each checked
mode in-place | new-guide
publishingMode draft (always, unless the user explicitly says publish)
A topic with no demand evidence is not a topic. Say so and offer to check it rather than writing anyway.
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.
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.
- 7d ago First seen · 309 lines · 126 tokens per session scan A a2acae48233c
content-thicken is a skill published in the GitHub repository Jasper0122/agent-seo-kit (6 stars, last pushed 16d ago), licensed MIT. It adds 126 tokens to every session and 3,547 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
fire-your-seo-agency
A procedure for improving how a website appears in search engines and how AI answer systems find and cite it. It covers search, answer-engine, generative-AI, and Naver visibility.
seo-audit
A checklist-based SEO review for a website. SEO, or search engine optimization, is the work of improving a site so search engines can understand and rank it.
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…
ultimate-seo-geo-skill
Use this skill when running SEO audits, optimizing for AI search engines (AI Overviews, ChatGPT, Perplexity), generating schema markup, diagnosing traffic drops, fixing Core Web Vitals, managing site migrations, or building keyword strategies. Runs scored full-site audits (0-100 Health Score) across 21 modules…
geo-content-research
Researches what prompts people ask AI engines (ChatGPT, Gemini, Perplexity, Claude) about a product category and produces a prompts.csv artifact — a prioritized, strictly-schema'd list of the queries where the brand should be cited. Feeds the monitor workflow.
create-geo-charts
Creates data visualizations (charts, graphs, tables) optimized for AI engine parsing and citation. Produces inline SVG/HTML with text summaries, data tables, and JSON-LD so AI engines can quote the data.