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 commands/fiale-plus/fiale-claude-plugins/team-syncgit clone --depth 1 https://github.com/fiale-plus/fiale-claude-pluginsWrote 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/fiale-plus/fiale-claude-plugins/team-sync)<a href="https://agentmods.dev/commands/fiale-plus/fiale-claude-plugins/team-sync"><img src="https://agentmods.dev/badge/commands/fiale-plus/fiale-claude-plugins/team-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 | $0.00017 | $0.00509 |
| Opus 5 | $0.00009 | $0.00254 |
| Sonnet 5 | $0.00003 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade B, and why
brain-team-sync scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ~/.claude/brain/config.json What it actually says
Pull latest changes from the team vault remote, and optionally push any local commits.
Steps
1. Read config
cat ~/.claude/brain/config.json
If team.enabled is false, say: "Team vault not configured. Run /brain-team-setup first." and stop.
Get team.vault_path and team.git_remote.
If git_remote is empty, say: "Team vault is local-only — no remote to sync with. To add a remote: /brain-team-setup." and stop.
2. Check git status
git -C <team_vault_path> status --short
git -C <team_vault_path> log --oneline origin/main..HEAD 2>/dev/null | head -5
Show current state:
- Any uncommitted changes
- Any local commits not yet pushed
3. Pull latest
git -C <team_vault_path> pull --ff-only origin main
If --ff-only fails (diverged history):
git -C <team_vault_path> fetch origin
git -C <team_vault_path> log --oneline HEAD..origin/main | head -10
Show what would be merged and ask:
"Remote has diverged. Use rebase? [y/n]"
If yes: git -C <team_vault_path> pull --rebase origin main
If no: show manual resolution instructions.
4. Show what's new
After pull, list recently changed files:
git -C <team_vault_path> log --oneline --name-only -10
Show new/changed knowledge items with a brief summary.
5. Push local commits (if any)
If there are local commits not yet on remote:
"Push N local commit(s) to remote? [y/n]"
If yes:
git -C <team_vault_path> push origin main
6. Report
✓ Team vault synced
Pulled: <N new commits> from remote
Pushed: <N commits | nothing to push>
Vault: <team_vault_path>
Remote: <git_remote>
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 · 79 lines · 17 tokens per session scan B 31a55a2d2049
brain-team-sync is a command published in the GitHub repository fiale-plus/fiale-claude-plugins (4 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 509 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
statusbar-theme
Switch the status-bar color theme (graphite / twilight / linen).
statusbar-preview
Render every style × theme combination using your real cached data.
statusbar-reset
Wipe the status-bar config back to defaults.
statusbar-doctor
Run cs doctor to diagnose why the status bar isn't showing what you expect.
statusbar
Show current status-bar config and list available styles + themes.