agentmods.dev

atom AGENTS.md

Repository instructions for Atom, a project-starter template rather than a finished application. They explain how to create a new project from the template or maintain the template itself.

In plain words
What is it for?
Use them when bootstrapping a project from Atom or adding improvements and shared guidance to the Atom template.
Why use it?
They tell a coding agent which project context to collect and which documentation and working modes to follow.

Instructions file for CodexOpenCode

2 2mo ago A scan 1,472 tokens original MIT
View the source file machbuilds/atom
Install

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.

agentmods
npx agentmods add instructions/machbuilds/atom/agents-md
Clone the repo
git clone --depth 1 https://github.com/machbuilds/atom

Made for: Codex, OpenCode.

Per session 1,472 This file is loaded in full into every session.
When invoked 1,472 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01472 $0.01472
Opus 5 $0.00736 $0.00736
Sonnet 5 $0.00294 $0.00294
Haiku 4.5 $0.00147 $0.00147

Measured yesterday against content hash e8683a3f0582, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

atom 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 yesterday.

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.

AGENTS.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md — atom

This is atom, a project-starter template. It is not an application. When you read this file, you are being asked to help bootstrap a NEW project from this template, OR to maintain the template itself by adding new learnings.

The name: every project starts from atom. Atom is the seed.

This file is the source of truth for AI tooling instructions. Tool-specific files (CLAUDE.md, GEMINI.md, .cursorrules, .github/copilot-instructions.md) are forwarders that point here.

Two modes you operate in here

Mode 1 — Bootstrap a new project

When the user says "let's start a new project from atom", or similar:

  1. Ask for project context first:

    • Project name and one-line description (what + why)
    • Primary stack/runtime (Next.js? Python? Swift? Other?)
    • Deploy target (Railway? Vercel? Fly? AWS? Custom? Don't know yet?)
    • Cost envelope expectations (per-request or monthly)
    • Solo build or multi-agent (Backend / Design / Test / Deploy split)?
    • Public-facing or internal-only?

  2. Read the docs in this order (you must, even if you've read them before on a different machine — they may have evolved):

    • docs/VOICE.md — how to write
    • docs/WORKFLOW.md — how the toolchain composes
    • docs/PATTERNS.md — reusable patterns to consider
    • docs/LESSONS_LEARNED.md — pain points to avoid
    • docs/HOW_TO_WRITE_CONSTITUTION.md — for the new project's constitution
    • docs/HOW_TO_PICK_DEPLOY_TARGET.md — only if user said "don't know yet"
    • docs/HOW_TO_DESIGN.md — only if the project has a UI

  3. Copy scaffold/ into the new project repo. The .github/, .claude/, .gitignore, package.json, AGENTS.md all go to the new repo's root. Docker files do NOT live in scaffold/ (Docker is fully optional).

  4. Ask the user which Docker tier (None / Dockerfile / + compose /

    • devcontainer) and copy the matching subset from extras/docker/. See extras/docker/README.md for the tier-to-file mapping. If the stack matches one in extras/<category>/<preset>/ and that preset ships a Dockerfile, prefer the stack-specific one over the generic.

Read the full file on GitHub · 125 lines

Changes

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.

  1. yesterday First seen · 125 lines · 1,472 tokens per session scan A e8683a3f0582

Subscribe to this mod's changes

atom AGENTS.md is an instructions file published in the GitHub repository machbuilds/atom (2 stars, last pushed 2mo ago), licensed MIT. It adds 1,472 tokens to every session, about $0.0074 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.

agentsmdai-agentai-toolsclaude-codeclideveloper-tools
Related

Other instructions, from other repositories

ai-workflow AGENTS.md

Instructions for cunhaax/ai-workflow, covering ai workflow template, rules — non-negotiable, project overview, commands and architecture.

cunhaax/ai-workflow · 2,602 tokens

trackly-cli CLAUDE.md

Claude Code instructions for trackly-app/trackly-cli, covering trackly-cli, tech stack, backend production source of truth, directory structure and key commands.

trackly-app/trackly-cli · 3,195 tokens

com-example-config-AsyncTestConfig

Instructions for PIsberg/vibetags, covering copilot instructions for asynctestconfig and immutable type.

PIsberg/vibetags · 82 tokens

pupila CLAUDE.md

Instructions for FranRom/pupila, covering claude.md, where things live, stack, run locally and repo layout.

FranRom/pupila · 4,040 tokens

claude-bridge AGENTS.md

Instructions for kadaba/claude-bridge, covering agents.md — using claude-bridge from any ai coding cli, two independent channels, 1. coordination (the conversation), 2. file transfer (the bytes) — same for every tool and workflows.

kadaba/claude-bridge · 1,505 tokens

UsageAtlas AGENTS.md

Instructions for SRX9/UsageAtlas, covering repository guidelines and coding approach.

SRX9/UsageAtlas · 41 tokens