Borrowing it
Nothing to install: this file belongs to gaia-react/gaia. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gaia-react/gaia/main/.claude/commands/gaia-serena-sync.mdgit clone --depth 1 https://github.com/gaia-react/gaiaWrote 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/gaia-react/gaia/gaia-serena-sync)<a href="https://agentmods.dev/commands/gaia-react/gaia/gaia-serena-sync"><img src="https://agentmods.dev/badge/commands/gaia-react/gaia/gaia-serena-sync.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.00053 | $0.00253 |
| Opus 5 | $0.00026 | $0.00127 |
| Sonnet 5 | $0.00011 | $0.00051 |
| Haiku 4.5 | $0.00005 | $0.00025 |
Grade A, and why
gaia-serena-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 6d 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.
What it actually says
Run the GAIA serena-sync workflow.
Pre-flight: Worktree check
This command rewrites the clone's .serena/project.yml language list, which is clone-level index configuration. If invoked from a linked worktree, reject hard: gaia_refuse_if_worktree (.gaia/scripts/main-only-lib.sh) asks the shared resolver which tree this is and refuses out loud, naming the main checkout, when the answer is a worktree.
Detection (run this first, before anything else):
. .gaia/scripts/main-only-lib.sh
gaia_refuse_if_worktree "/gaia-serena-sync" || exit 1
If the detection does not fire, fall through to the workflow dispatch line below.
Read .claude/skills/gaia/references/serena-sync.md from the project root and follow it exactly. No arguments are needed.
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.
- 6d ago First seen · 23 lines · 53 tokens per session scan A 80f290dfeacd
gaia-serena-sync is a command published in the GitHub repository gaia-react/gaia (23 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 253 once invoked, about $0.0003 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-30.
Other commands, from other repositories
deploy-release
Prepare and verify a staged or production deployment with rollback and smoke checks.
incident-hotfix
Mitigate a production incident or urgent regression first, then route to root-cause remediation and a postmortem.
publish-notes
Draft user-facing release notes, store changelogs, and internal publish summaries.
retro-learn
Convert delivery findings into skill, eval, workflow, and documentation improvements.
session-report
Capture delivery evidence, commands, changed files, blockers, and standards feedback after a work session.
traceability-audit
Map requirements, acceptance criteria, implementation, tests, and release artifacts into one traceability report.