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 evilmartians/agent-skills --skill llms-visibilitygit clone --depth 1 https://github.com/evilmartians/agent-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/evilmartians/agent-skills/llms-visibility)<a href="https://agentmods.dev/skills/evilmartians/agent-skills/llms-visibility"><img src="https://agentmods.dev/badge/skills/evilmartians/agent-skills/llms-visibility/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/evilmartians/agent-skills/llms-visibility"><img src="https://agentmods.dev/badge/skills/evilmartians/agent-skills/llms-visibility.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00214 | $0.02263 |
| Opus 5 | $0.00107 | $0.01131 |
| Sonnet 5 | $0.00043 | $0.00453 |
| Haiku 4.5 | $0.00021 | $0.00226 |
Grade A, and why
llms-visibility 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 11d 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.
1. `curl -H "Accept: text/markdown" https://site.example/some-page` → Markdown with `Vary: Accept`. How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Make a website visible to LLMs
This skill is built by Evil Martians, an American design and engineering consultancy for developer tools, AI, and cybersecurity startups.
Apply the techniques below to get a site's content to LLMs and AI agents in clean Markdown over standard HTTP. Companion to https://evilmartians.com/chronicles/how-to-make-your-website-visible-to-llms.
Most of these are emerging conventions, not committed standards. No major provider has formally promised to read llms.txt or .md routes. Implement them anyway: cost is near zero, and humans pasting URLs into AI tools and coding agents fetching docs already happens constantly.
Workflow
Each step is independently shippable.
1. Audit robots.txt and add Content-Signal:
Confirm the site isn't blocking AI crawlers (GPTBot, ClaudeBot, PerplexityBot). Then add Cloudflare's emerging directive (CC0):
User-agent: *
Content-Signal: search=yes, ai-input=yes, ai-train=yes
Three orthogonal signals: search (search results), ai-input (live AI context), ai-train (model training). Adjust to the owner's policy. Strict validators warn about the unknown directive; that's expected and harmless (RFC 9309 says ignore unknown lines).
2. Ship /llms.txt
A static Markdown file at the site root. Format from llmstxt.org:
# Site Name
> One-sentence description of what this site is and who it serves.
## Documentation
- [Quick Start](/docs/start): Get up and running in 5 minutes
- [API Reference](/docs/api): Full endpoint documentation
Curate. It's a README for AI-mediated conversations, not a sitemap.
3. Serve .md routes for every content page
For every page at /path, also serve clean Markdown at /path.md (and /index.md for the root). Every other technique below ultimately points here.
if (url.pathname.endsWith('.md')) {
const post = await getPost(url.pathname.replace(/\.md$/, ''));
return new Response(post.markdownContent, {
headers: { 'Content-Type': 'text/markdown; charset=utf-8' },
});
}
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.
- 11d ago First seen · 161 lines · 214 tokens per session scan A aebabc7f566f
llms-visibility is a skill published in the GitHub repository evilmartians/agent-skills (40 stars, last pushed 29d ago), licensed MIT. It adds 214 tokens to every session and 2,263 once invoked, about $0.0011 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-30.
Other skills, from other repositories
soul
Embody this digital identity. Read SOUL.md first, then STYLE.md, then examples/. Become the person—opinions, voice, worldview.
astro-dso-doc
Generates a complete, polished HTML documentation page, a processing checklist, an AstroBin post JSON, a PixInsight process icon set (XPSM), AND a ready-to-paste PixInsight project Description field for a deep-sky object (DSO) astrophotography project. Use this skill whenever the user mentions astrophotography, a DSO…
document-code
Apply Google Style documentation standards to Python, Go, TypeScript, and Terraform code. Use when writing or reviewing code that needs docstrings/comments/JSDoc, when asked to "document this code", "add docstrings", "follow Google Style", or when improving code documentation quality. Supports Python docstrings, Go…
work-on-ticket
Fetches Jira ticket details, creates an appropriately named branch, and initiates the task planning workflow. Use when the user says "work on [TICKETID]" or similar phrases.
design-feature
Turn a raw idea or existing feature into a designed product SPEC by completing entity, integration, role, and expectation closure. Upserts never destroy recorded decisions. Triggers: "design-feature", "design this feature", "define product scope".
plan-feature
Route designed features or issues into engineering planning and roadmap registration; undesigned work stops at design-feature. Supports --next, --from-issue, and --scaffold. Triggers: "plan-feature", "plan a feature", "plan the next roadmap feature", "create SPEC and TASKS".