Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/datacore-one/datacorenpx agentmods add commands/datacore-one/datacore/syncWrote 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/commands/datacore-one/datacore/sync)<a href="https://agentmods.dev/commands/datacore-one/datacore/sync"><img src="https://agentmods.dev/badge/commands/datacore-one/datacore/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/commands/datacore-one/datacore/sync"><img src="https://agentmods.dev/badge/commands/datacore-one/datacore/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.00004 | $0.02188 |
| Opus 5.5 | $0.00002 | $0.00875 |
| Sonnet 5.5 | $0.00001 | $0.00438 |
| Haiku 4.5 | $0.00000 | $0.00219 |
Grade A, and why
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 — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync
Command Context
When to Reference DIP-0010
Always reference when:
- Syncing with GitHub issues
- Routing external tasks to org-mode
- Handling sync conflicts
- Configuring sync adapters
Key decisions this DIP informs:
- Bidirectional sync workflow
- Conflict resolution strategy
- Task routing rules (labels → org tags)
Quick Reference
| Question | Answer |
|---|---|
| Repo sync? | ./sync shell script |
| Task sync? | DIP-0010 sync engine |
| Conflict log? | .datacore/state/sync_history.db |
| What DIPs govern this? | DIP-0010 (External Sync) |
Agents This Command Invokes
| Agent | Purpose |
|---|---|
| (none) | Uses shell scripts |
Integration Points
- DIP-0010 - External sync architecture
- /today - Auto-pulls on morning briefing
- /wrap-up - Auto-pushes on session close
Unified sync command for repositories and external task systems.
Usage
/sync # Full sync: repos + external tasks
/sync pull # Pull only (repos + external tasks)
/sync push # Push only (repos + external tasks)
/sync status # Show sync status
/sync tasks # Sync tasks only (skip repo sync)
Replaces: ./sync shell script (DIP-0010)
Behavior
Full Sync (/sync)
SYNC
====
1. Repository Sync
------------------
[Run git pull for all configured repos]
datacore (root).......... [PULLED/UP-TO-DATE/CONFLICT]
teamspace................ [PULLED/UP-TO-DATE/CONFLICT]
projectspace............. [PULLED/UP-TO-DATE/CONFLICT]
2. External Task Sync (DIP-0010)
--------------------------------
[If sync.tasks.enabled in settings.yaml]
Pulling external changes...
GitHub:
- datacore-one/datacore: [N] issues updated
- datacore-one/teamspace: [N] issues updated
Routing to org-mode...
- [N] tasks to inbox.org
- [N] tasks to next_actions.org (with :AI: tags)
Pushing org changes...
- [N] state changes synced
- [N] new tasks created in GitHub
3. Summary
----------
Repos: [X] synced, [Y] conflicts
Tasks: [X] pulled, [Y] pushed
Last sync: [timestamp]
SYNC COMPLETE
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 · 360 lines · 4 tokens per session scan A 9049f8f5f9d1
sync is a command published in the GitHub repository datacore-one/datacore (4 stars, last pushed yesterday), licensed MIT. It adds 4 tokens to every session and 2,188 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
linear-drain
Create the queued Linear projects and issues that shell scripts captured offline.
iteration-drive
Drive the active iteration to completion — Phase 2 Autonomous Execute, Phase 3 iteration-close, Phase 4 Create PR, Phase 5 PR merge-ready loop (prefer babysit/-babysit; optional greploop when repo has it; else CI fallback) until mergeable, then Phase 6 post-merge close once the PR is verified merged. Not Done until…
create-issue
Create a GitHub issue with proper template discovery and population.
prepare-release
Prepare a version release — follows project release config in .aicontext/release.md, runs first-time setup if config is missing.
run-task
Run pending steps, then aftertask finalization; does not close the task.
finish-task
Deprecated alias for close-task.