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.
git clone --depth 1 https://github.com/Smolevich/pet-project-atlasWrote 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/plugins/smolevich/pet-project-atlas/plugin)<a href="https://agentmods.dev/plugins/smolevich/pet-project-atlas/plugin"><img src="https://agentmods.dev/badge/plugins/smolevich/pet-project-atlas/plugin/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/plugins/smolevich/pet-project-atlas/plugin"><img src="https://agentmods.dev/badge/plugins/smolevich/pet-project-atlas/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
atlas 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 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.
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.
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "atlas",
"description": "Route a pet project through search, AI search, content, distribution and analytics.",
"version": "0.1.0",
"author": {
"name": "Smolevich"
},
"homepage": "https://atlas.smolevich.com",
"repository": "https://github.com/Smolevich/pet-project-atlas",
"license": "MIT",
"keywords": ["seo", "geo", "indexing", "analytics", "content"]
}
What it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 320 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 14 lines scan A b57e70d5ef76
atlas is a plugin published in the GitHub repository Smolevich/pet-project-atlas (2 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
claude-seo-geo
SEO + GEO skills for Claude Code that work like a specification: every page skill audits the page, benchmarks it against the competitors that rank, and builds the fix. Audit any site, diagnose a traffic drop, fix technical SEO, write content that ranks on Google and gets cited by ChatGPT, Perplexity and AI Overviews…
thl-open
AI-visibility engineering, the open way: the THL GEO / AI-search audit skill suite (citability, AI-crawler access, llms.txt, schema, brand mentions, technical, content, reporting) plus the THL-original agent-readiness-scan, organised around the THL GEO Method.
claude-rank
Claude Code plugin that tells you why your site won't get cited by AI — and fixes the discoverability files automatically.
geo-tool-check
AI search readiness checks (GEO): score any public page 0-100, see which AI crawlers robots.txt blocks, and score draft passages for citability. Same engine as geo-tool.com, runs locally, no account.
geo-lint
SEO & GEO content toolkit: /geo-lint validates content with 92 deterministic rules, /content-creator builds a self-configuring content pipeline with auto-discovery, brand voice, keyword research, and lint-fix validation until zero violations.
fire-your-seo-agency
Fire your SEO agency — a Claude Code skill that audits and implements SEO·AEO·GEO·LLMO·NEO(Naver) itself: crawler-eye audit, intent landing pages, llms.txt, structured data, Naver AI Briefing, a content engine (sub-blog, question backlog, publish gate, refresh), and a measurement loop.