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.
npx skills add richfrem/agent-plugins-skills --skill agent-file-synchronizationgit clone --depth 1 https://github.com/richfrem/agent-plugins-skillsWrote 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/skills/richfrem/agent-plugins-skills/agent-file-synchronization)<a href="https://agentmods.dev/skills/richfrem/agent-plugins-skills/agent-file-synchronization"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/agent-file-synchronization.svg" alt="Measured on agentmods" 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.00129 | $0.01414 |
| Opus 5 | $0.00064 | $0.00707 |
| Sonnet 5 | $0.00026 | $0.00283 |
| Haiku 4.5 | $0.00013 | $0.00141 |
Grade A, and why
agent-file-synchronization 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 today.
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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agent-file-synchronization
Identity
You synchronize project instruction files across modern AI tooling environments. Today, AGENTS.md is an open cross-tool standard (Codex, Cursor, Antigravity, and portable agents), while CLAUDE.md is used by Claude Code, GEMINI.md is used by Gemini CLI, and .github/copilot-instructions.md is used by GitHub Copilot.
A blind full-copy destroys platform-specific sections; this skill detects and re-preserves those
sections automatically instead of requiring a human to re-append them by hand. It also respects
repos that only want a subset of target files (via --targets) rather than forcing all 4 formats.
Scope: This skill owns mechanical replication. It does not own content quality
(optimize-agent-instructions) or initial project scaffolding (project-setup).
What gets preserved per target
| Target | Preserved section | Detected via |
|---|---|---|
GEMINI.md |
## Gemini CLI Tool Mapping table, appended at end of file |
Tail marker match |
.github/copilot-instructions.md |
# Copilot Instructions for <repo> header + authoritative blockquote |
Header lines before the shared body's first line |
AGENTS.md |
Open cross-tool standard (preserves custom header lines before anchor if any) | Header lines before anchor |
CLAUDE.md |
Anthropic Claude Code standard | Header lines before anchor |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed · +4 lines · -28 tokens per session 546a009b2a4d
- 3d ago First seen · 112 lines · 157 tokens per session scan A 22c5d3728584
agent-file-synchronization is a skill published in the GitHub repository richfrem/agent-plugins-skills (6 stars, last pushed today), licensed MIT. It adds 129 tokens to every session and 1,414 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
todos
Handle the agent personal todos.md file.
slip
Send AI-written text to a HUMAN outside this chat via a one-tap Slip note and reply with a single URL. Default: toss — a one-shot note (Markdown rendered, readable on open, tear-to-delete, auto-expires in 24 hours) for one-way delivery like checklists, summaries, code snippets. Use push only when the human is expected…
situate-what
Use when the user asks what is going on and needs a five-line summary of the session, branch, pull request, and ticket.
claude-nextsession
Schedule a set of instructions to run automatically once the current Claude Code usage session resets, using the local rate-limit cache (no API key needed). Trigger: "postpone this to next session", "run this once my usage resets", "queue this for later / after the reset", /claude-nextsession.
disk-reclaim
Reclaim disk space through a proof-gated plan — clears regenerable caches, merges proved-redundant copies, and protects agent history.
situate-brief
Use when confusion is only “huh,” “wait, what,” “sorry, you lost me,” or “slow down; explain simply and keep it short.”.