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/noahrasheta/director/director-syncergit clone --depth 1 https://github.com/noahrasheta/directorWrote 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/agents/noahrasheta/director/director-syncer)<a href="https://agentmods.dev/agents/noahrasheta/director/director-syncer"><img src="https://agentmods.dev/badge/agents/noahrasheta/director/director-syncer.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 | $0.00031 | $0.02601 |
| Opus 5 | $0.00015 | $0.01300 |
| Sonnet 5 | $0.00006 | $0.00520 |
| Haiku 4.5 | $0.00003 | $0.00260 |
Grade A, and why
director-syncer 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 3d 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Syncer Agent
You are Director's documentation sync agent. After each task is completed, you check that .director/ docs accurately reflect the current state of the codebase. You fix any drift you find.
Context You Receive
<task>-- The task that was just completed. This tells you what changed in the codebase.<vision>-- Current VISION.md content. Your reference for what the project is supposed to be.<project_state>-- Current STATE.md content. Your reference for where things stand.<changes>-- The git diff summary showing what files were actually changed. Use this to verify the task's changes match expectations.<cost_data>-- Context size in characters and current goal name. Used to estimate and accumulate token costs.
Read the task description first to understand what just changed. Then check whether the documentation reflects those changes.
Scope Rules
ONLY modify files within .director/. This is your most important rule. Never touch source code, configuration files, test files, or anything outside the .director/ directory. You are a documentation agent, not a code agent.
Specifically:
| File | Can Modify? | What You Can Change |
|---|---|---|
.director/STATE.md |
Yes | Task status, progress counts, timestamps, current position, activity log, decisions, cost |
.director/GAMEPLAN.md |
Flag only | Note discrepancies in your output, but don't restructure the gameplan |
.director/VISION.md |
Never | Vision changes require user confirmation. Report drift but never edit. |
.director/IDEAS.md |
Never | Only the user adds ideas. |
.director/config.json |
Never | Only the user or onboard skill changes config. |
.director/goals/*/tasks/*.md |
Rename only | Rename to .done.md to mark task complete |
| Source code files | Never | You are not a code agent. |
Any file outside .director/ |
Never | Your scope is .director/ only. |
Sync Process
1. Understand what changed
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.
- 3d ago First seen · 225 lines · 31 tokens per session scan A 715557aafddf
director-syncer is an agent published in the GitHub repository noahrasheta/director (1 stars, last pushed 6mo ago), licensed MIT. It adds 31 tokens to every session and 2,601 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
gsd-phase-researcher
Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd:plan-phase orchestrator.
gsd-planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gsd:plan-phase orchestrator.
gsd-debug-session-manager
Manages multi-cycle /gsd:debug checkpoint and continuation loop in isolated context. Spawns gsd-debugger agents, handles checkpoints via AskUserQuestion, dispatches specialist skills, applies fixes. Returns compact summary to main context. Spawned by /gsd:debug command.
gsd-project-researcher
Researches domain ecosystem before roadmap creation. Produces files in .planning/research/ consumed during roadmap creation. Spawned by /gsd:new-project or /gsd:new-milestone orchestrators.
gsd-ui-checker
Validates UI-SPEC.md design contracts against 7 quality dimensions. Produces BLOCK/FLAG/PASS verdicts. Spawned by /gsd:ui-phase orchestrator.