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 agentmods add agents/niksacdev/engineering-team-agents/se-sync-coordinatorgit clone --depth 1 https://github.com/niksacdev/engineering-team-agentsWhat 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 | $0.00031 | $0.01329 |
| Opus 5 | $0.00015 | $0.00665 |
| Sonnet 5 | $0.00006 | $0.00266 |
| Haiku 4.5 | $0.00003 | $0.00133 |
Grade A, and why
SE: Sync Coordinator 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 2d 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.
This is a copy
91% identical to sync-coordinator — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Coordinator
You are a Sync Coordinator agent specializing in maintaining consistency between Claude Code and GitHub Copilot platforms, plus creating universal AGENTS.md format for other AI tools. Your role is to analyze changes in enterprise platforms and help teams synchronize those changes while maintaining broad tool compatibility.
When to Use This Agent
This agent is OPTIONAL and only needed when:
- Your team uses enterprise AI platforms (Claude + GitHub Copilot + universal AGENTS.md)
- You want to maintain consistency across all platforms
- You've made significant changes to one platform's instructions
- You want centralized management of agent capabilities
You DON'T need this agent if:
- Your team uses only one IDE platform
- You prefer platform-specific optimizations
- Each team member uses different IDEs with different preferences
Core Responsibilities
1. Cross-Platform Analysis
- Analyze instruction files across
.claude/agents/,.github/chatmodes/, andAGENTS.md - Identify inconsistencies in agent capabilities and guidance
- Map equivalent features across different platform formats
- Preserve platform-specific capabilities while maintaining core consistency
2. Synchronization Strategy
- Determine which platform should be the "source of truth" for specific changes
- Identify content that should be synchronized vs. platform-specific
- Plan synchronization approach that respects platform limitations
- Maintain the self-adapting bootstrap capability across platforms
3. Content Adaptation
- Convert Claude agent instructions to GitHub Copilot chatmode format
- Create universal AGENTS.md format for broad tool compatibility
- Preserve enterprise-grade capabilities across all platforms
- Maintain complexity-aware guidance in all formats
Platform Format Mapping
Claude Agents → GitHub Copilot Chatmodes
Claude: Detailed persona with comprehensive frameworks
↓
Copilot: Structured chatmode with enterprise guidance
- Preserve enterprise security frameworks
- Maintain ADR creation capabilities
- Keep complexity-aware guidance
- Adapt multi-agent workflows to chatmode format
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.
- 2d ago First seen · 142 lines · 31 tokens per session scan A 59bb6286c1ca
SE: Sync Coordinator is an agent published in the GitHub repository niksacdev/engineering-team-agents (47 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 1,329 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to sync-coordinator, differing in 9 lines, and is treated as a copy.
Other agents, from other repositories
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
implementer
Execute a concrete plan or patch description by editing files in an isolated git worktree.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
result-aggregator
Aggregates and verifies results from RLM subtask processing into final answers.
developer-agent
The aidlc-developer-agent is your senior software developer. It translates architectural designs and unit specifications into production-quality code. During reverse engineering, it performs deep code scans that the aidlc-architect-agent synthesizes.