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 T4wroot/agentic-seo --skill githubgit clone --depth 1 https://github.com/T4wroot/agentic-seoWrote 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/t4wroot/agentic-seo/github)<a href="https://agentmods.dev/skills/t4wroot/agentic-seo/github"><img src="https://agentmods.dev/badge/skills/t4wroot/agentic-seo/github/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/t4wroot/agentic-seo/github"><img src="https://agentmods.dev/badge/skills/t4wroot/agentic-seo/github.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.00165 | $0.04298 |
| Opus 5.5 | $0.00066 | $0.01719 |
| Sonnet 5.5 | $0.00033 | $0.00860 |
| Haiku 4.5 | $0.00016 | $0.00430 |
Grade A, and why
github 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 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.
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.
This is a copy
100% identical to github — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platforms: GitHub
Guides GitHub for parasite SEO, GEO (AI citation), and curated list creation. GitHub is a Tier 2 Technical Authority platform—high domain authority, fast indexing, very high AI citation probability. Use for repos, README, GitHub Pages, gists, and Awesome-style navigation lists.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Why GitHub for SEO
| Factor | Effect |
|---|---|
| Domain authority | High DA; repos, gists, Pages rank well |
| Fast indexing | Search engines crawl GitHub frequently |
| AI citation | ChatGPT, Perplexity cite GitHub for technical queries; Tier 2 in GEO framework |
| Technical expertise | Strong expertise signals; structured docs become AI reference material |
| Cross-platform | Share across Dev.to, Stack Overflow, forums; amplifies visibility |
Use Cases
| Use case | Format | Purpose |
|---|---|---|
| Parasite SEO | Repos, README, Pages, gists | Leverage GitHub authority for rankings and backlinks |
| GEO | Documentation, tutorials, curated lists | AI tools cite GitHub for technical answers |
| Curated / navigation lists | Awesome-style repos | Topic-specific resource directories; backlinks, discovery |
Surfaces: profile vs repository
| Surface | What it is | Optimization focus |
|---|---|---|
| Profile README | Public repo with the same name as the username; root README.md renders on the profile |
Personal brand, flagship links, social proof |
| Pinned | Up to 6 repos or gists on the profile | Showcase top projects; align with entity signals (entity-seo) |
| Per-repo README | Root README.md on each repo’s Code tab |
Product landing; install, proof, CTAs |
Changing a normal repo README does not change the profile banner unless that content is the profile README repo or linked from it.
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 First seen · 327 lines · 165 tokens per session scan A 176e28b97e01
github is a skill published in the GitHub repository T4wroot/agentic-seo (15 stars, last pushed 1mo ago), licensed MIT. It adds 165 tokens to every session and 4,298 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to github, differing in 0 lines, and is treated as a copy.
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.
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…
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…
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…
optimise-seo
Use when explicitly authorized to implement a bounded, approved SEO action in a codebase or content system, verify the exact change, and report its limitations; do not use for broad audits, self-approved production changes, or outcome guarantees.