What is dotsync AGENTS.md?

Repository instructions for dotsync, a tool that keeps shell and configuration files synchronized across computers using Git and symbolic links. A symbolic link is a file reference that points to another file.

Use them when changing the command-line tool, dotfile mappings, installer, symlink behavior, or optional package-hardening scripts.

They prevent personal secrets from entering a public repository and preserve the project’s rules for portable, repeatable setup.

How adonyssantos/dotsync configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to adonyssantos/dotsync. 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/adonyssantos/dotsync/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/adonyssantos/dotsync

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/adonyssantos/dotsync/agents-md/github.svg)](https://agentmods.dev/instructions/adonyssantos/dotsync/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/adonyssantos/dotsync/agents-md"><img src="https://agentmods.dev/badge/instructions/adonyssantos/dotsync/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/adonyssantos/dotsync/agents-md"><img src="https://agentmods.dev/badge/instructions/adonyssantos/dotsync/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 772 This file is loaded in full into every session.

When invoked 772 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. ✓ AI security review Sonnet 5 · 7 Sept 2026 📄 Read the review

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.1	$0.00772	$0.00772
Opus 5.5	$0.00309	$0.00309
Sonnet 5.5	$0.00154	$0.00154
Haiku 4.5	$0.00077	$0.00077

Measured 2mo ago against content hash c57ce0e2d666, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

dotsync 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 2mo 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 · 65 lines

How it starts

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

AGENTS.md

Guidance for AI coding agents (Claude Code, Cursor, Copilot, Aider, …) working in this repository. Humans: see README.md.

What this project is

dotsync syncs a user's git/shell dotfiles across machines via a Git repo and symbolic links. It ships:

bin/dotsync — a dependency-free bash CLI (the core logic).
config/ — the dotfiles that get symlinked into $HOME.
sync.map — the manifest mapping config/* files to $HOME targets.
install.sh — an installer (works via curl | bash or from a local clone).
scripts/secure-packages.sh — optional npm hardening.

Golden rules

Never commit real personal data. No real names, emails, tokens, SSH keys, API keys, hostnames, or machine-specific paths. Config files must ship with placeholders (Your Name, [email protected], your-username).
This is a public template. Keep everything generic and portable. Prefer feature-detection (command -v foo) over hardcoding tools or OSes.
Symlink, never copy. The whole value proposition is that edits flow back into the repo. Don't replace ln -s with cp.
Keep changes idempotent. link, unlink, and install.sh must be safe to run repeatedly. Back up before overwriting; restore on unlink.
No new runtime dependencies. The CLI is intentionally plain bash so it runs anywhere. Don't introduce Node, Python, or package managers to run it.

Conventions

Bash scripts start with #!/usr/bin/env bash and set -euo pipefail.
Use the existing info/ok/warn/die helpers in the CLI for output.
Adding a new synced dotfile = add the file under config/ and a line to sync.map. Files appended to an rc file (not symlinked, like bashrc.aliases) use BEGIN/END markers so they can be cleanly removed.
Document any new alias in the README tables and any new command in the CLI reference table.

Before you finish

Run these checks and make sure they pass:

bash -n bin/dotsync install.sh scripts/secure-packages.sh   # syntax
shellcheck bin/dotsync install.sh scripts/secure-packages.sh # if available

# End-to-end smoke test against a throwaway HOME (never your real one):
TMP="$(mktemp -d)"
HOME="$TMP" DOTSYNC_DIR="$PWD" bash bin/dotsync link
HOME="$TMP" DOTSYNC_DIR="$PWD" bash bin/dotsync doctor
HOME="$TMP" DOTSYNC_DIR="$PWD" bash bin/dotsync unlink
rm -rf "$TMP"

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

2mo ago First seen · 65 lines · 772 tokens per session scan E c57ce0e2d666

Subscribe to this mod's changes

dotsync AGENTS.md is an instructions file published in the GitHub repository adonyssantos/dotsync (40 stars, last pushed 4mo ago), licensed MIT. It adds 772 tokens to every session, about $0.0031 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-30.

Git and workflow dotfiles git-config-sync sync-config

dotsync AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
dotsync AGENTS.mdadonyssantos/dotsync	Instructions file	40	4mo ago	MIT	A	772	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

dotsync: Instructions file for Codex