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 Hadi99K/AGENT_SKILLS --skill init-agent-syncgit clone --depth 1 https://github.com/Hadi99K/AGENT_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/hadi99k/agent_skills/init-agent-sync)<a href="https://agentmods.dev/skills/hadi99k/agent_skills/init-agent-sync"><img src="https://agentmods.dev/badge/skills/hadi99k/agent_skills/init-agent-sync/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/skills/hadi99k/agent_skills/init-agent-sync"><img src="https://agentmods.dev/badge/skills/hadi99k/agent_skills/init-agent-sync.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.00020 | $0.00604 |
| Opus 5.5 | $0.00008 | $0.00242 |
| Sonnet 5.5 | $0.00004 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
init-agent-sync 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 1mo 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
- Create an
AGENT_SYNC.mdfile in the root of the project if one doesn't exist. - Populate it with standard AI agent instructions, context tracking, a session task board, and a handoff log.
- Set up the foundation for multi-agent workflows so AI assistants can cleanly hand off tasks to one another.
When to use me
Use this when starting a new project, or when you want to introduce the AI agent synchronization system to an existing repository.
Execution Steps
When invoked, execute the following steps:
- Check for existing file: Check if
AGENT_SYNC.mdalready exists in the project root. If it does, inform the user and ask if they want to overwrite it. - Create the file: Use the Write tool to create
AGENT_SYNC.mdwith the following template:
# 🤖 Agent Synchronization & Handoff Hub
**⚠️ INSTRUCTIONS FOR ALL AI AGENTS ⚠️**
1. **Read this file first** upon waking up or starting a new session.
2. **Check the Handoff Log** for context, recent changes, and messages directed at you.
3. **Master Trackers:** Always consult `progress.md` (or equivalent) for the *master project roadmap*. This file (`AGENT_SYNC.md`) is specifically for inter-agent communication, technical handoffs, and session-level tasks.
4. **Task Management:** When you start a task, update the Short-Term Tasks section (mark as `[~] In Progress`). When finished, mark as `[x] Completed`.
5. **Session Wrap-up:** Before ending your session or asking the user to switch agents, **append a brief summary** of what you accomplished and any blockers to the **Handoff Log**.
---
## 🎯 Current Context & Technical State
- **Active Branch:** `main`
- **Current Phase:** Initial Setup
- **Master Reference:** `progress.md`
---
## 📋 Session Task Board (Granular / Short-Term)
*Note: High-level goals live in master trackers. Use this for immediate, technical sub-tasks.*
- [ ] Define initial tasks here
---
## 💬 Handoff & Discussion Log
*Format: `**[YYYY-MM-DD] - [User/Agent Name]:** Message @Mention`*
**[Current Date] - Setup Agent:**
### Session Summary: Hub Initialization
**Objectives Accomplished:**
1. Initialized the AGENT_SYNC.md coordination hub.
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.
- 1mo ago First seen · 62 lines · 20 tokens per session scan A ab912b45ba89
init-agent-sync is a skill published in the GitHub repository Hadi99K/AGENT_SKILLS (3 stars, last pushed 4d ago), licensed MIT. It adds 20 tokens to every session and 604 once invoked, about $0.0001 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 skills, from other repositories
openspec-bulk-archive-change
Archive multiple completed OpenSpec changes at once. Use when archiving several parallel changes. Also use for a plural archive request - "openspec bulk-archive", "opsx bulk-archive", "openspec archive all", or "openspec archive these changes".
openspec-bulk-apply-change
Use when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated verification and no merge.
stakeholder-communication-and-status-updates
Guides writing narrative-style stakeholder status updates and strategy memos instead of bullet-point decks, grounded in Amazon's 6-page narrative memo discipline. Use when the user asks to "write a status update," "draft a weekly update for stakeholders," "write a project update email," "prepare a 6-pager," "turn…
planning-and-task-breakdown
Breaks an existing spec or clear requirement into a dependency-ordered, sized task list with checkpoints and parallelization notes. Use when a task feels too large to start, when scope needs estimating, or when work can be split across parallel agents/sessions. For a single lightweight plan document for one request…
spec-driven-development
Writes a structured, human-reviewed specification before any code, deriving implementation from that written contract rather than from a vague request. Use when starting a new project or feature with no spec yet, when requirements are ambiguous or only exist as an idea, or before an architectural decision on a change…
constraint-driven-development
Use when an Android project has no written quality bar, when the user says "set up constraints" or "define our standards", when coverage, performance, or accessibility should become enforced gates instead of per-PR arguments, when an agent keeps silencing checks or skipping tests to get to green, or when a threshold…