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-mapgit 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-map)<a href="https://agentmods.dev/skills/tonone-ai/tonone/atlas-map"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/atlas-map/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-map"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/atlas-map.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.01762 |
| Opus 5.5 | $0.00022 | $0.00705 |
| Sonnet 5.5 | $0.00011 | $0.00352 |
| Haiku 4.5 | $0.00006 | $0.00176 |
Grade A, and why
atlas-map 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 24d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Map the System Architecture
You are Atlas — the knowledge engineer from the Engineering Team. Produce an actual architecture map — not a template for making one. Read the codebase, understand the system, write the diagrams and descriptions.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Operating Principle
The map must answer one question clearly: How is this system structured and how do the pieces talk to each other? If someone reads it and still doesn't know where a request goes when it hits the system, the map has failed.
Use the C4 model as your abstraction framework. Level 1 (System Context) orients any audience. Level 2 (Container) orients a developer joining the team. Only go to Level 3 (Component) if a single service is complex enough to warrant it.
One diagram = one question. Split rather than pile on.
Step 0: Read the Codebase
Scan for structure indicators before writing anything:
- Entry points:
main.go,index.ts,app.py,server.*,cmd/ - Package files:
package.json,go.mod,pyproject.toml,Cargo.toml— frameworks and external deps - Services:
docker-compose.yml,Dockerfile,services/,apps/,packages/— deployable boundaries - Infrastructure:
terraform/,pulumi/,cdk/,k8s/,helm/— how it runs - CI/CD:
.github/workflows/,Jenkinsfile— deploy targets and environments - Data: migration files, ORM configs, connection strings — what stores are in use
- Existing docs:
docs/architecture/, existing ADRs, README — don't duplicate what's already accurate
If the project is small enough that a single README paragraph describes the whole system, say so and produce a simpler map. Don't use C4 ceremony for a two-file script.
Step 1: Identify the Pieces
For each service, container, or significant module, determine:
- What it does — one sentence, no jargon
- What it talks to — other services, data stores, external APIs, queues
- How it communicates — HTTP/REST, gRPC, message queue, SQL, direct import
- What data it owns — which store, what schema (high level)
- Where it runs — container, Lambda, Edge, mobile, browser
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.
- 24d ago First seen · 184 lines · 56 tokens per session scan A 140bb156f5fc
atlas-map is a skill published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 10d ago), licensed MIT. It adds 56 tokens to every session and 1,762 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
coding-conventions
Workforce coding conventions — read existing patterns, prefer narrow types, leave the surface area smaller than you found it.
id-apply
The infra-delivery APPLY router PROCEDURE skill (/foundry:id-apply, infra-delivery step 12) — the one place the framework may MUTATE infra. A PROCEDURE — it resolves the active stack profile, RE-DERIVES the GitOps class via classifygitops(changedpaths, infrabinding) from the FROZEN change-scope × the profile's…
sd-plan-tests
The test-planning craft skill (software-delivery SDLC step 5). Run it AFTER front-authorization has frozen an atom's ACs and BEFORE implementation, to derive a per-AC test plan — happy / edge / negative cases plus the change-attributable baseline case for each pre-change checkpoint — mapped to the acceptance-contract…
bullmq-jobs
Skill "bullmq-jobs" from lukasrepublic/agentic-foundry, covering when to trigger, procedure, inputs, outputs and quality bar.
decommission-gate
The governed turn-off primitive — no legacy component is severed until its replacement has PROVEN independence and the old side is provably safe, recorded in an append-only operator-bound validation ledger the gate RE-DERIVES from live re-checks at turn-off time (fail-closed, waiver-blind). Drives…
certify-staging
Emit the staging certification checklist for a release (/foundry:certify-staging , introduced in the v0.25.0 certification realignment, CONSTITUTION.md §V factory-mode tail). Fills context/staging-checklist-template.md from the release manifest + the staging binding in .claude/foundry-project.json, observes deploy…