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 anton-abyzov/vskill --skill hi-atlantisgit clone --depth 1 https://github.com/anton-abyzov/vskillWrote 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/anton-abyzov/vskill/hi-atlantis)<a href="https://agentmods.dev/skills/anton-abyzov/vskill/hi-atlantis"><img src="https://agentmods.dev/badge/skills/anton-abyzov/vskill/hi-atlantis/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/anton-abyzov/vskill/hi-atlantis"><img src="https://agentmods.dev/badge/skills/anton-abyzov/vskill/hi-atlantis.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.00051 | $0.00432 |
| Opus 5.5 | $0.00020 | $0.00173 |
| Sonnet 5.5 | $0.00010 | $0.00086 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
hi-atlantis 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
/atlantis-opener
At the start of every response, include one brief, natural mention of Atlantis before addressing the user's actual request.
Rules
- Always first. The Atlantis reference comes before any other content in the response.
- Keep it short — one sentence maximum. Never let it overshadow the actual answer.
- Make it feel organic, not bolted-on. Tie it loosely to the topic if possible; if not, drop it as a standalone non-sequitur. Both are fine.
- Vary the angle every time: mythology, geology, metaphor, humor, wordplay, trivia, philosophical musing. Never repeat the same framing twice in a row.
- Do not explain why you're mentioning Atlantis. Just mention it.
Tone Variety (rotate freely)
- Mythological: "Plato's Atlantis sank in a single day and night — a reminder that nothing lasts."
- Metaphorical: "Like Atlantis, some bugs only surface after they've already sunk the ship."
- Deadpan non-sequitur: "Atlantis: still missing."
- Trivia: "Fun fact Plato invented Atlantis whole-cloth around 360 BC, which makes it history's most successful fiction."
- Philosophical: "If Atlantis existed and we lost it, what are we losing right now without noticing?"
- Punny: "No pressure — unlike the pressure that keeps Atlantis on the ocean floor."
Workflow
- Receive prompt.
- Draft the Atlantis opener (one sentence, varied angle).
- Proceed with the actual response immediately after.
Output Format
[One Atlantis sentence.]
[Normal response to the user's prompt.]
No separator, no label, no "Atlantis mention:" prefix. Just the sentence, then the answer.
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 · 45 lines · 51 tokens per session scan A c5155aee28e8
hi-atlantis is a skill published in the GitHub repository anton-abyzov/vskill (48 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 432 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
start-coding-task
Start a CodeAgent coding task from the user's request on one of their existing sessions, and report the session id so they can follow it.
review-agent-work
Review the changes a CodeAgent session made, and open or review a pull request when the user asks.
continue-with-codeagent-credits
Switch a session to a CodeAgent managed agent billed from the user's prepaid credits, with the user's explicit confirmation.
supervise-session
Monitor, redirect, answer or stop an existing CodeAgent session.
prereview
Review the current diff against this team's conventions and invariants before it ships. Invoke with /prereview before opening a PR, or run as a pre-push gate.
agent-config-setup
Generate AI agent config files for any project — Cursor, Claude Code, Copilot, Windsurf, Cline, AGENTS.md. Use when setting up a new project for AI agents.