smm-sync: Instructions file for Codex

AGENTS.md

smm-sync AGENTS.md is an instructions file for Codex, OpenCode from varunajaytawde28-design/smm-sync. It costs 938 tokens per session, scanned A, original, MIT.

A project instruction file named AGENTS.md that tells coding agents how the smm-sync repository works. It documents the architecture, the source of truth, and how agents claim files and handle changes.

In plain words
What is it for?
Use it when an agent works on smm-sync, especially when editing project instructions, refreshing shared context, claiming files, or reviewing coordinated changes.
Why use it?
It gives agents consistent rules for working together in one codebase and helps prevent silent overwrites or conflicting edits.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Claude Code; mentions AGENTS.md.

This is varunajaytawde28-design/smm-sync's own configuration. It tells Codex and OpenCode how to work on smm-sync 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 smm-sync configures →

Reuse

Borrowing it

Nothing to install: this file belongs to varunajaytawde28-design/smm-sync. 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/varunajaytawde28-design/smm-sync/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/varunajaytawde28-design/smm-sync

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 smm-sync AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/varunajaytawde28-design/smm-sync/agents-md"><img src="https://agentmods.dev/badge/instructions/varunajaytawde28-design/smm-sync/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 938 This file is loaded in full into every session.
When invoked 938 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.00938 $0.00938
Opus 5 $0.00469 $0.00469
Sonnet 5 $0.00188 $0.00188
Haiku 4.5 $0.00094 $0.00094

Measured 10d ago against content hash 749de3b41266, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

smm-sync 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 10d 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 · 88 lines

How it starts

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

This is the canonical source of truth for AI agents working on this project.

AGENTS.md — smm-sync

Source of truth for this project. Edit this file directly. Run smm refresh after editing.

Project

smm-sync: Coordination layer for simultaneous AI agents working on the same codebase. Automatically parses shared context from AGENTS.md and coordinates file ownership using Tuple Space protocol + propose-validate-commit event log.

Stack: python 3.11+, click, jinja2, filelock, mcp

Architecture

AGENTS.md is the source of truth (not smm.toml)

Why: The ecosystem has standardised on AGENTS.md. We exploit this instead of fighting it. Ingesting AGENTS.md directly eliminates the translation layer and makes SMM-Sync work with any project that already has AGENTS.md.

os.rename() for file claiming

Why: POSIX-atomic on both macOS and Linux. No external dependency, no daemon required, works in the same filesystem namespace.

Propose-validate-commit replaces LWW CRDT

Why: Silent overwrites destroy trust between agents. Explicit rejection with reasons lets agents surface conflicts to the human. The event log is auditable history.

events.jsonl is append-only

Why: Append-only logs are crash-safe. Any interrupted write produces a malformed last line, not a corrupted file. Replay is deterministic.

MCP server is the interface boundary

Why: MCP is how Claude Code connects to tools. Exposing coordination via MCP means agents can claim files and read context without any special integration — just call the tool.

Constraints

  • Python 3.11+ only
  • No network calls except MCP server binding to localhost
  • coordinator.py os.rename() logic must not be touched
  • state.json must remain human-readable JSON
  • Every public function must have a docstring with input/output types

Danger Zones

  • Do not use os.rename() across filesystems — only atomic within the same filesystem
  • events.jsonl must never be truncated or rewritten — append only
  • The MCP server uses a global _smm_dir — not safe for multi-project serving
  • Do not write computed fields into AGENTS.md — it is the source of truth

Read the full file on GitHub · 88 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. 10d ago First seen · 88 lines · 938 tokens per session scan A 749de3b41266

Subscribe to this mod's changes

smm-sync AGENTS.md is an instructions file published in the GitHub repository varunajaytawde28-design/smm-sync (1 stars, last pushed 5mo ago), licensed MIT. It adds 938 tokens to every session, about $0.0047 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.

Related

Other instructions, from other repositories

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,296 tokens

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,153 tokens

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

spec-kit AGENTS.md

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,104 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

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,469 tokens