agentmods.dev

atom: Instructions file for Codex

AGENTS.md

atom AGENTS.md is an instructions file for Codex, OpenCode from machbuilds/atom. It costs 1,472 tokens per session, scanned A, original, MIT.

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

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions CLAUDE.md; mentions AGENTS.md; built for gbrain.

This is machbuilds/atom's own configuration. It tells Codex and OpenCode how to work on atom itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything atom configures →

not rated 2repo 4mo ago A scan 1,472 tokens original MIT
View source ↗ machbuilds/atom
Reuse

Borrowing it

Nothing to install: this file belongs to machbuilds/atom. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/machbuilds/atom/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/machbuilds/atom

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for atom AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/machbuilds/atom/agents-md/github.svg)](https://agentmods.dev/instructions/machbuilds/atom/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/machbuilds/atom/agents-md"><img src="https://agentmods.dev/badge/instructions/machbuilds/atom/agents-md/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.

agentmods 80×15 button for atom AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/machbuilds/atom/agents-md"><img src="https://agentmods.dev/badge/instructions/machbuilds/atom/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.01472 $0.01472
Opus 5.5 $0.00589 $0.00589
Sonnet 5.5 $0.00294 $0.00294
Haiku 4.5 $0.00147 $0.00147

Measured 1mo ago against content hash e8683a3f0582, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

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. 1mo ago 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 4mo ago), licensed MIT. It adds 1,472 tokens to every session, about $0.0059 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-08-31.

Claude Codeagentsmdai-agentai-toolsclideveloper-tools
Related

Other instructions, from other repositories

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).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens