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 cartoonitunes/inlay-skills --skill ai-readiness-auditgit clone --depth 1 https://github.com/cartoonitunes/inlay-skillsWrote 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/cartoonitunes/inlay-skills/ai-readiness-audit)<a href="https://agentmods.dev/skills/cartoonitunes/inlay-skills/ai-readiness-audit"><img src="https://agentmods.dev/badge/skills/cartoonitunes/inlay-skills/ai-readiness-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/cartoonitunes/inlay-skills/ai-readiness-audit"><img src="https://agentmods.dev/badge/skills/cartoonitunes/inlay-skills/ai-readiness-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.00055 | $0.00978 |
| Opus 5 | $0.00028 | $0.00489 |
| Sonnet 5 | $0.00011 | $0.00196 |
| Haiku 4.5 | $0.00006 | $0.00098 |
Grade A, and why
ai-readiness-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 12d 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.
curl -s -X POST https://www.inlay.dev/api/audit \ How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Readiness Audit Skill
Audit any website for AI agent readiness using the Inlay API. Checks 11 categories including llms.txt, MCP servers, structured data, semantic HTML, meta quality, and more.
Quick Start
Ask the user for a URL, then run the audit:
curl -s -X POST https://www.inlay.dev/api/audit \
-H 'Content-Type: application/json' \
-d '{"url":"TARGET_URL"}'
Or use the wrapper script:
bash scripts/audit.sh "https://example.com"
Workflow
Step 1: Get the Target URL
Ask the user which website to audit. Accept any valid URL.
Step 2: Run the Audit
curl -s -X POST https://www.inlay.dev/api/audit \
-H 'Content-Type: application/json' \
-d '{"url":"TARGET_URL"}'
The API returns a JSON response with:
score— overall score (0-100)grade— letter gradecategories— per-category scores and findingsrecommendations— actionable fixes sorted by priorityboostScore— projected score after applying Inlay Boost (if available)
Step 3: Present the Report
Format the results as a clear report. See examples/sample-report.md for the expected format.
Report structure:
- Header — Site URL, overall score, letter grade
- Grade Scale — A+ (90-100), A (80-89), B (70-79), C (60-69), D (40-59), F (0-39)
- Category Breakdown — Table with each category's score and status
- Top Issues — Negative findings that hurt the score
- Recommendations — Actionable fixes sorted by impact (high → low)
- Inlay Boost — Projected score if Inlay Boost data is available
Step 4: Offer to Fix Issues
After presenting the report, offer to fix issues automatically:
- llms.txt missing → Use the
setup-llms-txtskill to create one - No MCP server → Use the
setup-mcp-serverskill to set one up - Missing structured data → Generate JSON-LD schema markup
- Poor meta tags → Rewrite title/description for AI discoverability
- Missing robots.txt directives → Add AI bot permissions
- No sitemap → Generate or update sitemap.xml
What ships with it
4 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.
- 12d ago First seen · 115 lines · 55 tokens per session scan A 4376c7adfb2e
ai-readiness-audit is a skill published in the GitHub repository cartoonitunes/inlay-skills (1 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 978 once invoked, about $0.0003 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…