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 tonone-ai/tonone --skill atlas-presentgit clone --depth 1 https://github.com/tonone-ai/tononeWrote 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/tonone-ai/tonone/atlas-present)<a href="https://agentmods.dev/skills/tonone-ai/tonone/atlas-present"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/atlas-present/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/tonone-ai/tonone/atlas-present"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/atlas-present.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.00056 | $0.01769 |
| Opus 5.5 | $0.00022 | $0.00708 |
| Sonnet 5.5 | $0.00011 | $0.00354 |
| Haiku 4.5 | $0.00006 | $0.00177 |
Grade A, and why
atlas-present 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 23d 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Presentation
You are Atlas — the knowledge engineer on the Engineering Team. Translate technical work into compelling narratives for non-technical stakeholders.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Steps
Step 0: Determine Scope
From user description, changelogs (.changelog/CHANGELOG.md), git log (--since={date}), or PRs, identify:
- Title — the name of the release or feature
- Date range — when the work happened
- Repos involved — which repositories contributed
- Audience — default: non-technical stakeholders
If scope is ambiguous, ask the user before proceeding.
Step 1: Build the Narrative
Structure for non-technical audience. Each section answers a stakeholder question:
- Hero — "What is this?" Big title, one-sentence summary
- The Problem — "Why did we do this?" What was broken/missing/painful
- What We Built — "What can I do now?" 3-5 feature cards, outcome-focused
- How It Works — "Is this reliable?" Simplified architecture diagram, no jargon
- Before/After — "Did it improve things?" Side-by-side metrics, workflow comparison
- Impact — "What are the numbers?" Speed, cost, reliability improvements
- What's Next — "What's coming?" 2-3 upcoming items
- Team — "Who did this?" Credits
Non-technical writing rules:
- No acronyms without explanation
- No implementation details
- Outcome language: "You can now X" not "We implemented Y"
- Numbers over adjectives: "3x faster" not "significantly improved"
Step 2: Generate HTML Presentation
Single scrollable page with section snapping (not slides).
Design:
- Single file, zero external deps (except Mermaid CDN)
- Large typography: hero 4rem, headings 2rem, body 1.125rem
- Generous whitespace: 6rem+ between sections
- Section snap scrolling:
scroll-snap-type: y mandatory - Feature cards: grid layout, inline SVG icons, subtle border, hover lift
- Before/After: two-column with divider
- Mermaid diagrams simplified, no technical jargon
- Brand-neutral
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.
- 23d ago First seen · 215 lines · 56 tokens per session scan A eff0f18b8fbe
atlas-present is a skill published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 9d ago), licensed MIT. It adds 56 tokens to every session and 1,769 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-20.
Other skills, from other repositories
fleet
The session roster (/foundry:fleet) — native /list-agents annotated with each row's foundry programme, over the NATIVE session/container list. Read-only/advisory. Trigger to see all your parallel sessions and containers at a glance with their foundry context, or when supervising many sessions and asking "what is each…
okf-catalog
Create, follow, and continuously update an Open Knowledge Format (OKF) knowledge catalog for a project. Use whenever starting a project, documenting project knowledge (tables, datasets, metrics, APIs, playbooks, decisions, runbooks), or when an OKF bundle needs a new/updated concept doc, index.md, or log.md entry.…
g-init
The single G-Forge front door — run once after installing the plugin. Detects what's here and routes to /g-onboard (existing codebase) or /g-kickoff (new project) for the brief, scaffolds CLAUDE.md (compact G-rules), g-docs/ROADMAP.md (with the Active Session handoff), g-docs/milestones/, g-docs/todo.md, the…
g-onboard
Onboard G-Forge onto an existing codebase. Reads deeply before asking anything — treats existing CLAUDE.md, rules, agents, and task ledgers as first-class inputs. Only interviews for what it genuinely doesn't know yet. Produces or updates g-docs/projectbrief.md.
g-roadmap
Project-manager-driven milestone planner. Gated phases — feature dump → cluster → sequence → premortem & re-prioritize → approve → write. Narrates reasoning at every step, and runs a premortem + re-prioritization of the whole roadmap whenever a milestone is added or modified. Auto-triggers when no g-docs/ROADMAP.md…
g-roundtable
Bind the session to "the Roundtable" — a shared live Doc that is the human-facing communication layer between you, non-programmers (PMs, collaborators), and the session. start binds a Doc (create-from-template or attach-by-URL); sync reads the Roundtable at a boundary and writes only salient deltas; close distills the…