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 elie222/atom-eve --skill agent-readmegit clone --depth 1 https://github.com/elie222/atom-eveWrote 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/elie222/atom-eve/agent-readme)<a href="https://agentmods.dev/skills/elie222/atom-eve/agent-readme"><img src="https://agentmods.dev/badge/skills/elie222/atom-eve/agent-readme/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/elie222/atom-eve/agent-readme"><img src="https://agentmods.dev/badge/skills/elie222/atom-eve/agent-readme.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.00083 | $0.01640 |
| Opus 5 | $0.00042 | $0.00820 |
| Sonnet 5 | $0.00017 | $0.00328 |
| Haiku 4.5 | $0.00008 | $0.00164 |
Grade A, and why
agent-readme 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent READMEs
A README is the human's install decision: what this agent does for me. It is not the agent's prompt (instructions.md, addressed to the agent), and it is not the setup guide (SETUP.md, which owns env, config, and the wiring walkthrough). It carries only what is unique to this agent. Everything derivable the catalog page already renders, so repeating it is the slop to cut.
The shape
The README is the manifest in YAML frontmatter, an H1, and exactly one section. No lead paragraph, and never a ## Setup section: the build rejects one.
---
description: <one outcome-led sentence; the catalog card>
category: <an id from taxonomy.json>
integrations: [<display tags>]
---
# <Title>
## What it does
<lead line: the outcome the agent delivers. Then the concrete actions as short bullets, and what you get back.>
Frontmatter fields: description, category, integrations, and optionally author, dependencies (npm packages the agent needs), and skills (remote skill refs). Everything else is derived by the build, never authored: name (the directory), title (the H1), family (taxonomy via category), connections (from agent/connections/*.ts).
The build requires the H1, ## What it does, and a valid category. The one-line description is what the catalog page renders at the top, and it feeds cards and SEO; write it outcome-led, not led by the mechanism, framework, or backend. Don't append "Agent" to the H1 unless it is part of a proper name.
Setup never lives here. Credentials, config, and the wiring walkthrough belong in SETUP.md (its frontmatter declares env and config; its body is the walkthrough). The README may close "What it does" with a single pointer line, Setup lives in [SETUP.md](./SETUP.md)., and nothing more.
For an external template, the README is the whole entry: frontmatter with a source: block (type: external-template, repo, url, cloneUrl) plus the H1 and ## What it does. No SETUP.md, no agent/. Do not summarize the upstream setup, credentials, or runtime steps; the external repo owns those details.
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 · 112 lines · 83 tokens per session scan A c45df26e195d
agent-readme is a skill published in the GitHub repository elie222/atom-eve (49 stars, last pushed 2mo ago), licensed MIT. It adds 83 tokens to every session and 1,640 once invoked, about $0.0004 per session on Opus 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-08-30.
Other skills, from other repositories
seo-audit
How to present the deterministic AI-SEO audit returned by auditpage. Use when reporting a page's readability and citation-readiness for AI answer engines (ChatGPT, Claude, Perplexity).
workspace
How to safely operate the sandboxed workspace. Use for any multi-step task involving files or shell commands.
research
Iterative, self-evaluating web research. Use when answering open-ended questions that require gathering and verifying information from multiple sources.
writing-quality
Writing-quality guardrails for any prose the agent drafts or edits: blog posts, page copy, Notion drafts, release notes, marketing text. Use this skill whenever writing or revising content meant for humans to read, to keep the prose natural, plain, and free of AI-sounding phrasing. Not needed for code, queries, or…
sanity-best-practices
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this skill…
portable-text-serialization
Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown…