What is dots AGENTS.md?

A set of project instructions for AI coding assistants working on the dots command-line tool, including its planning rules, setup steps, and development commands.

Use it when developing, building, testing, or planning changes for the dots repository. It covers Go installation, linting, testing, and the dots install and update commands.

It gives an assistant the project context and tells it when to read specifications before making changes, reducing guesswork during coding.

dots AGENTS.md — Instructions file by drn

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/drn/dots/agents-md

Clone the repo

git clone --depth 1 https://github.com/drn/dots

Made for: Codex, OpenCode.

Per session 4,627 This file is loaded in full into every session.

When invoked 4,627 The same file — it is already loaded in full.

Security scan B 2 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.

Model	Per session	Once invoked
Fable 5	$0.04627	$0.04627
Opus 5	$0.02313	$0.02313
Sonnet 5	$0.00925	$0.00925
Haiku 4.5	$0.00463	$0.00463

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

Security

Grade B, and why

dots AGENTS.md scanned grade B with 2 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

| agents | Agent skills, custom agents, hooks, and status line (symlinks agents/skills → ~/.claude/skills + ~/.agents/skills, agents/custom → ~/.claude/agents, agents/AGENTS.md → ~/.claude/CLAUDE.md, registers hooks and

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

| pi | pi.dev coding agent CLI + config (installs pi via curl pi.dev/install.sh, symlinks pi/agent/models.json → ~/.pi/agent/models.json, and seeds defaultProvider/defaultModel for Ollama qwen3:32b in ~/.pi/agent/setting

AGENTS.md · 293 lines

How it starts

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

OpenSpec Instructions

These instructions are for AI assistants working in this project.

Always open @/openspec/AGENTS.md when the request:

Mentions planning or proposals (words like proposal, spec, change, plan)
Introduces new capabilities, breaking changes, architecture shifts, or big performance/security work
Sounds ambiguous and you need the authoritative spec before coding

Use @/openspec/AGENTS.md to learn:

How to create and apply change proposals
Spec format and conventions
Project structure and guidelines

Keep this managed block so 'openspec update' can refresh the instructions.

AGENTS.md

This file provides essential context for AI assistants working with the dots repository.

Quick Start

Build and run the CLI:

go install ./...
dots

Essential Commands for Development

Building & Testing

go install ./...                              # Build all binaries
revive -set_exit_status ./...                # Run linter

Core CLI Commands

dots install all                              # Full system setup
dots install <component>                      # Install specific component
dots update                                   # Update configuration
dots doctor                                   # Run diagnostics

Spec-Driven Development (OpenSpec)

Route every spec-worthy change through openspec/ before writing code. Any behavioral change — new CLI command or component, changed install/update behavior, new skill/custom agent/hook, an altered convention or invariant — gets a change folder first:

Create openspec/changes/<name>/ with proposal.md, delta specs under specs/<capability>/spec.md, and tasks.md. Use a kebab-case, verb-led change-id (add-, update-, remove-, refactor-).
Run openspec validate <name> --strict and get approval before implementing.
Implement against the tasks, keeping deltas in sync as requirements shift.
Archive within the same PR, before merge — run openspec archive <name> --yes (or apply it by hand: merge the delta requirements into the base specs under openspec/specs/<capability>/ and move the change folder to openspec/changes/archive/<YYYY-MM-DD>-<name>/) and commit the result on the change branch. Squash-merge applies the work immediately, so the base-spec update must land atomically with the PR — do NOT leave archiving as a separate post-merge step (that strands the base specs behind shipped code).

Read the full file on GitHub · 293 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.

2d ago First seen · 293 lines · 4,627 tokens per session scan B b588d666d9e0

Subscribe to this mod's changes

dots AGENTS.md is an instructions file published in the GitHub repository drn/dots (23 stars, last pushed 3d ago), licensed MIT. It adds 4,627 tokens to every session, about $0.0231 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Languages Planning Testing

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.

openai/codex · 5,182 tokens

buildNext

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 · 6,785 tokens

dots AGENTS.md