agentmods.dev

dotfiles AGENTS.md

Repository instructions for maintaining a dotfiles project, a collection of personal configuration files. They define the authoritative documentation, editing requirements, validation commands, and cleanup rules.

In plain words
What is it for?
Use them before editing to read the required guidance, follow repository standards, run lint and tests, update related documentation, and complete the specified Git cleanup after merging.
Why use it?
They give coding agents a single source of truth and reduce inconsistent changes, missed checks, and leftover branches or worktrees.

Instructions file for CodexOpenCode

5 2d ago A scan 385 tokens original Apache-2.0
View the source file brujack/dotfiles
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/brujack/dotfiles/agents-md
Clone the repo
git clone --depth 1 https://github.com/brujack/dotfiles

Made for: Codex, OpenCode.

Per session 385 This file is loaded in full into every session.
When invoked 385 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.00385 $0.00385
Opus 5 $0.00192 $0.00192
Sonnet 5 $0.00077 $0.00077
Haiku 4.5 $0.00038 $0.00038

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

Security

Grade A, and why

dotfiles 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 · 30 lines

What it actually says

AGENTS.md

Cursor agent instructions for this repo.

Source of truth (exhaustive)

  • CLAUDE.md is exhaustive and authoritative for this repository.
  • Treat all rules in CLAUDE.md as required, not advisory.
  • If this file and CLAUDE.md conflict, follow CLAUDE.md.
  • Also apply global Cursor rules from ~/.cursor/rules/ when they do not conflict.

Required compliance behavior

  • Before editing, read relevant sections in CLAUDE.md.
  • During implementation, follow the repository's exact standards for shell style, idempotency, install guards, profile/capability usage, and symlink strategy.
  • After changes, run the validations required by CLAUDE.md (make lint, make test, and targeted suites as applicable).
  • Keep docs in sync when required by CLAUDE.md (including README.md and CLAUDE.md updates).

Dotfiles-specific must-follow items

  • After a feature PR merges: always complete post-merge cleanup — remove any linked worktree for that branch, delete the branch locally and on origin, then git fetch --prune and git pull on master. See .claude/standards/git-workflow.md (Feature Branches step 5).
  • Preserve selective Cursor user linking: only settings.json, keybindings.json, and snippets from .cursor/User.
  • Do not introduce broad linking of volatile/local editor state.
  • Preserve pre-commit and pre-push hook behavior and CI conventions.
  • Never commit local-only state or secrets (for example config/local.sh, credentials, tokens, or machine-local caches).

Drift control

  • When CLAUDE.md changes, update this file in the same change so both remain aligned.
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 · 30 lines · 385 tokens per session scan A 00f619fd7498

Subscribe to this mod's changes

dotfiles AGENTS.md is an instructions file published in the GitHub repository brujack/dotfiles (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 385 tokens to every session, about $0.0019 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.

Code reviewGit and workflowTesting
Related

Other instructions, from other repositories

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

next.js 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,296 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit 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.

github/spec-kit · 7,040 tokens

langchain 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,345 tokens