Borrowing it
Nothing to install: this file belongs to julien777z/agent-sync-action. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/julien777z/agent-sync-action/main/AGENTS.mdgit clone --depth 1 https://github.com/julien777z/agent-sync-actionWrote 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.
[](https://agentmods.dev/instructions/julien777z/agent-sync-action/agents-md)<a href="https://agentmods.dev/instructions/julien777z/agent-sync-action/agents-md"><img src="https://agentmods.dev/badge/instructions/julien777z/agent-sync-action/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.
<a href="https://agentmods.dev/instructions/julien777z/agent-sync-action/agents-md"><img src="https://agentmods.dev/badge/instructions/julien777z/agent-sync-action/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.02380 | $0.02380 |
| Opus 5.5 | $0.00952 | $0.00952 |
| Sonnet 5.5 | $0.00476 | $0.00476 |
| Haiku 4.5 | $0.00238 | $0.00238 |
Grade A, and why
agent-sync-action 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Generated by Agent Sync Action. Do not edit this file directly.
Canonical guidance lives in .agents/.
GitHub Rules
Workflows
- Keep
runsteps declarative. Invoke checked-in scripts for control flow, validation, filesystem changes, or other implementation logic instead of embedding arbitrary shell or program code in workflow YAML; place those scripts under.github/scripts/and prefer Python. - Do not hard-code runtime versions when a shared action, reusable workflow, or repository version file supplies them; omit
python-versionwhen shared Python automation provides it, and usenode-version-file: ".nvmrc"for Node.js workflows. - Do not add glue steps that only read versions or forward setup data. Pass repository-owned version files and inputs directly to the action that uses them whenever supported.
- Keep workflow files concise: merge related setup and dependency commands into one clearly named generic step when their execution order and conditions allow it. Do not split tool or package installation into separate steps merely by dependency.
- Environment configuration that tunes a tool — retry counts, timeouts, cache locations, path entries — belongs in the step that installs or runs that tool, not in a step of its own. A step whose whole body writes to
$GITHUB_ENVis named for a concern rather than an action, and the reader has to look elsewhere to find out which later step it affects. Write those exports at the end of the owning step so the setting and its consumer stay together. - Add an explanatory comment when an edge case requires an explicit version override.
- Use version-tagged GitHub Actions such as
actions/checkout@v4andactions/setup-python@v5, not full commit SHAs.
Branches and Pull Requests
- Keep pull requests focused and give them descriptive titles and descriptions; request appropriate reviewers when the repository workflow requires them.
- A pull request description covers the changes in that pull request and nothing else. Leave out alternatives considered and rejected, work deferred to a later change, and the reasoning behind not doing something.
- Repositories are independent. A pull request in one repository does not describe, reference, or explain changes made in another.
- When additional work arrives on a non-default branch, retain that branch and add the work to its pull request even when the task could be reviewed independently.
- Query the current branch's pull request before creating one. Reuse it while it is open, or create one from the current branch when none exists.
- Create a separate branch only when the user asks or the current branch's pull request is already merged; start post-merge work from the default branch.
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.
- 5d ago Changed · +11 lines · +106 tokens per session fa3236693113
- 1mo ago Changed · -997 lines · -14,459 tokens per session scan B → A 477f022108d8
- 1mo ago Changed · +5 lines · +39 tokens per session 03408a6b0cad
- 2mo ago First seen · 1,166 lines · 16,694 tokens per session scan B 4bf00119faf4
agent-sync-action AGENTS.md is an instructions file published in the GitHub repository julien777z/agent-sync-action (9 stars, last pushed 3d ago), licensed MIT. It adds 2,380 tokens to every session, about $0.0095 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-31.
Other instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.