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 ZensInk/zens-ink-seo-package --skill site-auditgit clone --depth 1 https://github.com/ZensInk/zens-ink-seo-packageWrote 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/zensink/zens-ink-seo-package/site-audit)<a href="https://agentmods.dev/skills/zensink/zens-ink-seo-package/site-audit"><img src="https://agentmods.dev/badge/skills/zensink/zens-ink-seo-package/site-audit/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/zensink/zens-ink-seo-package/site-audit"><img src="https://agentmods.dev/badge/skills/zensink/zens-ink-seo-package/site-audit.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.00127 | $0.00800 |
| Opus 5.5 | $0.00051 | $0.00320 |
| Sonnet 5.5 | $0.00025 | $0.00160 |
| Haiku 4.5 | $0.00013 | $0.00080 |
Grade A, and why
site-audit 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 2d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Site audit on the build output
Audits run against the built dist/ directory — deterministic, offline,
repeatable in CI. Three tools, three altitudes: site-wide technical, per-page
quality, per-draft gate.
When to use
- "Audit my site for SEO problems" (any static site)
- Pre-launch checklist on a fresh build
- A page won't rank and nobody knows why
- CI gate: fail the build when quality drops
When NOT to use
- Sites behind login or rendered only client-side with no static output — there is no dist/ to read.
Setup
pip install zens-ink
cd the-site-repo && npm run build # produce dist/ first
Commands
# 1. Site-wide technical audit (broken links, meta, images, canonicals)
python3 -m zens_ink.site_audit --dist dist
python3 -m zens_ink.site_audit --dist dist --format json --output audit.json
# 2. Per-page on-page quality, 7 dimensions, 0-100
python3 -m zens_ink.onpage_audit --dist dist
python3 -m zens_ink.onpage_audit --dist dist --keywords keywords.txt
# 3. Pre-publish gate for markdown drafts (exit 1 below score 70)
python3 -m zens_ink.content_qc drafts/ --min-score 70
How to read the results
Work the report top-down — it is ordered by blast radius:
- Broken links / 404s — fix first, they waste crawl budget and trust.
- Missing canonical / H1 / meta description — quick wins, one file each.
- Image size flags — above
--max-image-kb(default generous), compress. - On-page scores — anything under ~70 has a concrete reason listed; fix the named dimension, not the score.
content_qc in a CI pipeline: --min-score 70 makes low-quality drafts
fail the build. Will AI engines cite this draft? is the question it answers
(BLUF presence, structure, quotable facts).
Known false positive: sitemap-index style sitemaps from Astro may parse as 0 URLs — if the audit reports zero sitemap URLs on an Astro site, ignore the sitemap section; the link/meta findings are still valid.
Next steps
- Audit clean but still not ranking →
keyword-difficulty(it may be the keyword, not the site). - Make the site AI-citable →
geo-readinessskill.
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.
- 2d ago First seen · 87 lines · 127 tokens per session scan A c5b956da44c1
site-audit is a skill published in the GitHub repository ZensInk/zens-ink-seo-package (53 stars, last pushed 3d ago), licensed MIT. It adds 127 tokens to every session and 800 once invoked, about $0.0005 per session on Opus 5.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-10-15.
Other skills, from other repositories
altorank
Run AltoRank through its hosted MCP server: readiness audits, Search Console, keyword research, and SEO drafts into a review queue.
content-creator
Self-configuring content creation pipeline with geo-lint validation. On first use, scans your project to learn its framework, content schema, categories, and authors, then creates SEO & GEO-optimized content matched to your brand voice. Validates every piece with geo-lint's 92 rules until zero violations. Triggers on…
geo-lint
SEO & GEO content linter — validates Markdown/MDX files for AI search visibility using 92 deterministic rules (35 GEO, 32 SEO, 14 content quality, 8 technical, 3 i18n). Runs an autonomous lint-fix loop: scan content, read structured violations, fix them, re-lint until clean. Use when optimizing content for AI…
geo-platform-optimizer
Platform-specific AI search optimization — audit and optimize for Google AI Overviews, ChatGPT, Perplexity, Gemini, and Bing Copilot individually.
vs-search-tuning-specify-policy-direction
Viking Search tuning for specified policy directions. Use this when the user provides specific queries, a type of query, or a business policy direction, and asks to boost, suppress, or fix a class of search results through request-parameter passthrough. You must only perform read-only baseline evaluation and…
vs-search-tuning-partial-case
Use when the user provides 1-50 concrete bad-case search queries for one Viking Search app and wants local deterministic fixes. This skill only verifies request-level fine-operation interventions against a read-only baseline scene and delivers a console-ready configuration sheet, validated payloads, and a replay…