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 bemoshiur/OmniRank --skill auditgit clone --depth 1 https://github.com/bemoshiur/OmniRankWrote 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/bemoshiur/omnirank/audit)<a href="https://agentmods.dev/skills/bemoshiur/omnirank/audit"><img src="https://agentmods.dev/badge/skills/bemoshiur/omnirank/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/bemoshiur/omnirank/audit"><img src="https://agentmods.dev/badge/skills/bemoshiur/omnirank/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.00049 | $0.00731 |
| Opus 5.5 | $0.00020 | $0.00292 |
| Sonnet 5.5 | $0.00010 | $0.00146 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
audit scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`.next/server/app/*.html` or a raw `curl`, never a browser inspector. How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit
Score a site across four layers — SEO, AEO, GEO, and crawl hygiene — and produce a prioritised, actionable fix list.
When to use
Anything shaped like "is this site discoverable?" Ranking complaints, schema questions, pre-deploy verification, or "why doesn't ChatGPT cite us?"
When NOT to use
- Generating
llms.txt/facts.json— that isgeo-artifacts. - Writing schema or AnswerBlocks — that is
aeo-onpage(planned, not in v0.1.0). - Submitting URLs for indexing — that is
indexing(planned, not in v0.1.0). - Off-site, backlink, or entity work — that is
offsite-entity(planned, not in v0.1.0).
Audit only diagnoses. It never edits the site.
omnirank fix shows the diff it would apply for the four mechanical findings and
writes nothing — there is no --write flag. Run it to answer "which file is
wrong?", then hand the diff to a human.
How to run it
# Zero-config, any live site
python3 -m omnirank.cli audit https://example.com
# Configured repo, CI-ready
python3 -m omnirank.cli audit --config omnirank.config.json --fail-on h1 canonical schema
Exit codes: 0 clean, 1 a configured gate failed, 2 usage or config error.
The JSON report lands in .omnirank/reports/<date>-audit.json.
--fail-on takes gate names (h1, canonical, title-length, llms-txt,
facts-json, schema, ...), not finding ids — see references/gates.md for the
full name list and how ids relate to them.
Reading the output
Work findings in severity order — every error before any warning. Each finding carries
observed, expected, and fix; quote the fix when proposing the change, and cite the
id so it can be tracked across runs.
Scores are 100 - 10×errors - 3×warnings per layer, floored at zero. A layer with no
findings is absent from the score map rather than scored 100 — never report a score for a
layer whose gates did not run.
Rules
- Never claim a gate passed if it could not be evaluated. An unreachable URL is an error, not a skip.
- Audit the built HTML, not the hydrated DOM. Crawlers see server output. Check
.next/server/app/*.htmlor a rawcurl, never a browser inspector. - Do not fix during an audit. Produce the list, then hand off.
- Report the numbers you got. If the score is 41, say 41.
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.
- 1mo ago First seen · 67 lines · 49 tokens per session scan A 5ec260d8d810
audit is a skill published in the GitHub repository bemoshiur/OmniRank (10 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 731 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
seo-vertical-detect
Classify a website as ecommerce, local-business, blog-publisher, saas, docs, or generic (multiple may apply), and report detected locales, from the persisted PageSnapshot plus the platform detector's vertical hints. Used by seo-orchestrator to decide which conditional modules to run and how to reweight the scores.
seo-fix-apply
Writer protocol preloaded into the seo-fixer-writer agent — how confirmed SEO/AI-search fixes are applied (git pre-flight, backup, Edit/Write for local diffs, ticketed adapter CLIs for remote targets, re-verify, publish only on a second ticket, rollback) and the findings-array output contract. Used only by the fix…
audit
Audit a website or web codebase for SEO and AI-search (GEO/AEO) — produces two independent 0-100 scores (Search SEO + AI Visibility) plus a prioritized, evidence-backed report persisted on disk. Read-only; never writes to the project. Use when the user asks to audit, analyze, check, or score a site's SEO, structured…
web-optimization
Audit or generate web content optimized for traditional search (SEO), AI generative answer engines like ChatGPT/Perplexity/Google AI Overviews (GEO), and answer engines / featured snippets / voice (AEO). Use when the user asks to improve a page's ranking or AI-citability, run an SEO/GEO/AEO audit of a URL or file, add…
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.
ansvisor-aeo-coach-standalone
Standalone (no-MCP) version of the Ansvisor AEO Coach. Use this only when the user's Claude client cannot connect to the Ansvisor MCP server (e.g. claude.ai web without a Connector configured). Fetches live data from the Ansvisor REST API directly with the user's API key via code execution — visibility, competitors…