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 ouranos-labs/pseolint --skill aeogit clone --depth 1 https://github.com/ouranos-labs/pseolintWrote 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/ouranos-labs/pseolint/aeo)<a href="https://agentmods.dev/skills/ouranos-labs/pseolint/aeo"><img src="https://agentmods.dev/badge/skills/ouranos-labs/pseolint/aeo/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/ouranos-labs/pseolint/aeo"><img src="https://agentmods.dev/badge/skills/ouranos-labs/pseolint/aeo.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.00000 | $0.01077 |
| Opus 5 | $0.00000 | $0.00539 |
| Sonnet 5 | $0.00000 | $0.00215 |
| Haiku 4.5 | $0.00000 | $0.00108 |
Grade A, and why
aeo 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Answer-engine optimization, with teeth
Search is splitting in two: classic ranking, and being the source an AI answer cites. AEO (a.k.a. GEO) is optimizing for the second. The May 2026 spam-policy revision put manipulation of AI answers explicitly in scope, so the upside and the risk are both real.
This skill is different from generic AEO advice: every recommendation maps to a
pseolint aeo/* rule you can actually run. You don't hope a page is
citable; you run pseolint and the rule tells you.
The AEO checklist: each line is an enforced rule
Thresholds live in the engine and drift; cite the rule and let
pseolint --explain <rule> (or the MCP rule resource) give the current number.
- Lead with the answer. A direct, self-contained answer (≈ first 300 chars,
in a
<p>right under the heading) is what gets extracted. Enforced byaeo/answer-first. - Be citable, not vague. Concrete, attributable facts: numbers, dates,
named sources: are what AI engines quote. Enforced by
aeo/citable-facts. - Don't bait, deliver. Headlines that promise an answer the body never gives
get skipped (and look spammy). Enforced by
aeo/summary-bait. - Modular, extractable structure. Self-contained sections under clear
headings extract cleanly; walls of prose don't. Enforced by
aeo/content-modularity. - Answer the actual questions. Real FAQ coverage of the query's sub-questions.
Enforced by
aeo/faq-coverage. - Show freshness. Visible, structured publish/modified dates: AI answers
favor current sources. Enforced by
aeo/freshness-signals. - Let the answer engines in. Don't block AI crawlers (GPTBot, PerplexityBot,
Google-Extended, ClaudeBot) in robots. Enforced by
aeo/crawler-access(honorsAllowper RFC 9309). - Ship
llms.txt. A machine-readable map of your canonical, citable content. Enforced byaeo/llms-txt.
Verify: don't eyeball it
# Crawl the site and get the per-page AEO findings
npx pseolint https://yoursite.com
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 · 83 lines · 0 tokens per session scan A d346c2dba9e3
aeo is a skill published in the GitHub repository ouranos-labs/pseolint (6 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,077 tokens. 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
portaljs-check-data-quality
Audit a local or remote tabular file (CSV/TSV) for common data quality issues — schema, nulls, types, duplicates. Read-only. Use when a dataset needs a quality check before publishing, or a showcase renders wrong (blank cells, garbled numbers, an unsortable date column) and the cause needs isolating.
omd-apply
A skill that applies a project's DESIGN.md file as visual and brand guidance for interface work. It covers components, colors, fonts, layout, copy, motion, and visual assets.
audit-website
Audit a website with the squirrelscan CLI and fix the findings in code. Runs SEO, performance, security, technical, content, accessibility, and 15 other rule categories (260+ rules), returns an LLM-optimized report, then drives an iterative fix loop, mapping issues to source files, applying fixes, and re-auditing…
suiko
A Japanese writing and review workflow for checking whether text sounds uniform, translated, unnatural, or difficult to read. It supports writing and editing documents such as reports, guides, meeting notes, proposals, and emails.
updater
Check Claude Code changelog for lintable changes and implement cclint updates. Use when a new Claude Code version ships, when CLAUDE.md claudecodelastupdated is stale, or for version gap detection, domain classification, and parallel agent dispatch across CUE schemas, hook events, known tools, and lint rules.
schliff
Deterministic linter and scorer for instruction files — SKILL.md, AGENTS.md, CLAUDE.md. No model in the loop: the same bytes score the same everywhere. Use for linting, scoring, auditing or CI-gating an instruction file, and for checking whether the commands a file promises actually resolve in the repo. Trigger…