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 agentmods add instructions/avinashp/agentsatlas/agents-mdgit clone --depth 1 https://github.com/AvinashP/AgentsAtlasWhat 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 | $0.00297 | $0.00297 |
| Opus 5 | $0.00148 | $0.00148 |
| Sonnet 5 | $0.00059 | $0.00059 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
AgentsAtlas AGENTS.md 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 2d 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
Atlas Workflow
Use Atlas skills as thin routers to canonical Claude command docs.
Planning State
.planning/STATE.mdtracks current status, active phase, and current plan file..planning/ROADMAP.mddefines milestones/phases and target outcomes..planning/phases/{NN}-PLAN.mdstores the active executable phase plan..planning/phases/{NN}-SUMMARY.mdstores execution outcomes and deviations.
Skills to Use
atlas-init: Initialize project workflow artifacts.atlas-plan: Create executable phase plan.atlas-execute: Execute current plan tasks.atlas-status: Check project progress.atlas-sync: Restore context after /clear.atlas-triage: Pull and triage external issues.atlas-complete: Complete current milestone.atlas-review: Review code changes.
Canonical Command Docs
commands/atlas/init.mdcommands/atlas/plan.mdcommands/atlas/execute.mdcommands/atlas/status.mdcommands/atlas/sync.mdcommands/atlas/triage.mdcommands/atlas/complete.mdcommands/atlas/review.md
Sync Workflow Artifacts
- Source of truth:
commands/atlas/manifest.json - Re-generate wrappers/docs/plugin command list:
node scripts/sync-atlas-artifacts.mjs
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.
- 2d ago First seen · 38 lines · 297 tokens per session scan A d69852291977
AgentsAtlas AGENTS.md is an instructions file published in the GitHub repository AvinashP/AgentsAtlas (7 stars, last pushed 3mo ago), licensed MIT. It adds 297 tokens to every session, about $0.0015 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-31.
Other instructions, from other repositories
gangsta GEMINI.md
Instructions for kucherenko/gangsta, a project described as: AI agentic skills framework for spec-driven development, built on the organizational model of mafia.
truthmark CLAUDE.md
Instructions for merlinhu1/truthmark, covering authority, documentation scope, product boundary, rules and instruction surface boundary.
Skillry GEMINI.md
Gemini CLI instructions for FluxonLab/Skillry, covering gemini.md, prime directives, 1. inspect first, 2. coding principles and 3. security & safety (non-negotiable).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.