agentmods.dev

context-sync: Instructions file for Codex

AGENTS.md

context-sync AGENTS.md is an instructions file for Codex, OpenCode from Intina47/context-sync. It costs 449 tokens per session, scanned A, original, MIT.

Repository instructions are a guide for coding agents working on a TypeScript project. They describe the folders, commands, code style, and available testing approach.

In plain words
What is it for?
Use them when modifying the project, choosing the right development command, naming files, or deciding how to test changes.
Why use it?
They reduce guesswork about how the project is organized and how changes should be built, run, and checked.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

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

not rated 190repo 6mo ago A scan 449 tokens original MIT
View source ↗ Intina47/context-sync
Reuse

Borrowing it

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/intina47/context-sync/agents-md"><img src="https://agentmods.dev/badge/instructions/intina47/context-sync/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 449 This file is loaded in full into every session.
When invoked 449 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.00449 $0.00449
Opus 5.5 $0.00180 $0.00180
Sonnet 5.5 $0.00090 $0.00090
Haiku 4.5 $0.00045 $0.00045

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

Security

Grade A, and why

context-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 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 · 36 lines

What it actually says

Repository Guidelines

Project Structure & Module Organization

  • src/: TypeScript source for the MCP server and integrations.
  • bin/: CLI setup and install scripts (Node CJS).
  • docs/: User documentation (CONFIG.md, TOOLS.md, DATA.md, TROUBLESHOOTING.md).
  • assets/: Static assets used in docs.
  • dist/: Build output generated by tsc (do not edit by hand).

Build, Test, and Development Commands

  • npm run build: Compile TypeScript to dist/.
  • npm run dev: Run the server from source via tsx.
  • npm run watch: Run with file watching (tsx watch).
  • npm start: Run the built server from dist/.
  • npm run setup: Launch interactive setup (bin/setup.cjs).
  • npm test: Smoke test that prints readiness (no test runner).

Coding Style & Naming Conventions

  • Language: TypeScript (ES2022 modules), strict mode enabled in tsconfig.json.
  • Indentation: 2 spaces (match existing formatting).
  • File naming: kebab-case in src/ (e.g., git-context-engine.ts).
  • Prefer explicit, descriptive function names; keep modules focused.

Testing Guidelines

  • No automated test suite is defined. npm test is a placeholder.
  • If you add tests, keep them close to the feature area and document how to run them.

Commit & Pull Request Guidelines

  • Commit messages follow Conventional Commits (examples: feat:, fix:, perf:, refactor:, chore(release):).
  • PRs should include: a short description, rationale, and any user-facing changes. Link related issues when applicable. Add screenshots only for docs/UI changes.

Configuration & Release Notes

  • User config and platform integration details live in docs/CONFIG.md.
  • Update docs/RELEASE_NOTES.md when shipping user-facing changes.
  • prepublishOnly runs npm run build && npm test, so keep those scripts passing before publish.
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. 2mo ago First seen · 36 lines · 449 tokens per session scan A 20ef8e907892

Subscribe to this mod's changes

context-sync AGENTS.md is an instructions file published in the GitHub repository Intina47/context-sync (190 stars, last pushed 6mo ago), licensed MIT. It adds 449 tokens to every session, about $0.0018 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.

context-managementcontext-syncdeveloper-toolsmcp-serversqliteworkspace
Related

context-sync AGENTS.md compared with instructions from other repositories

context-sync AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
context-sync AGENTS.mdIntina47/context-syncInstructions file1906mo agoMITA449Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode