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 kostja94/openblog --skill audit-seogit clone --depth 1 https://github.com/kostja94/openblogWrote 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/kostja94/openblog/audit-seo)<a href="https://agentmods.dev/skills/kostja94/openblog/audit-seo"><img src="https://agentmods.dev/badge/skills/kostja94/openblog/audit-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/kostja94/openblog/audit-seo"><img src="https://agentmods.dev/badge/skills/kostja94/openblog/audit-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.00014 | $0.00099 |
| Opus 5 | $0.00007 | $0.00049 |
| Sonnet 5 | $0.00003 | $0.00020 |
| Haiku 4.5 | $0.00001 | $0.00010 |
Grade A, and why
audit-seo 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 9d 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.
What it actually says
Moved: audit-seo → validate-blog-seo
This skill was renamed to clarify scope: blog module SEO validation only, not site-wide SEO audit.
Use instead: skills/validate-blog-seo/SKILL.md
Update any agent rules or references from audit-seo to validate-blog-seo.
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.
- 9d ago First seen · 13 lines · 14 tokens per session scan A df9681ccd1d2
audit-seo is a skill published in the GitHub repository kostja94/openblog (6 stars, last pushed 11d ago), licensed MIT. It adds 14 tokens to every session and 99 once invoked, about $0.0001 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
repo-seed
Seed, audit, adopt, and progressively evolve an agent-native repository with risk-triggered specs, durable decisions, resident governance skills, capability state, deterministic gates, and safe upgrades. Use when initializing or upgrading a repository, when an unmanaged repository grows complex, or when delivery…
Blog Outline Generator
Generates a detailed, SEO-optimized blog post outline with H2/H3 structure, key points per section, and a hook.
Technical Blog Post Writer
Writes engaging, accurate technical blog posts targeted at developer audiences.
repo-review
Use when reviewing a pull request or a change in this repository — orients the reviewer to this repository's standards (AGENTS.md conventions, decision log, gates) and the review-specific checks that code alone cannot show.
repo-decisions
Use when a change chooses among meaningful alternatives whose rationale may be revisited, or when writing, updating, reviewing, or superseding a MADR record.
repo-governance
Use when repository complexity, delivery, ownership, security, release, or incident signals change; when governance may be missing; or when adding, reviewing, deferring, or upgrading repo-seed capabilities.