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-setupgit 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-setup)<a href="https://agentmods.dev/commands/fiale-plus/fiale-claude-plugins/team-setup"><img src="https://agentmods.dev/badge/commands/fiale-plus/fiale-claude-plugins/team-setup.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.01610 |
| Opus 5 | $0.00009 | $0.00805 |
| Sonnet 5 | $0.00003 | $0.00322 |
| Haiku 4.5 | $0.00002 | $0.00161 |
Grade B, and why
brain-team-setup 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 How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up or reconfigure the team knowledge vault. The team vault is a git-backed directory that holds decisions, patterns, and gotchas shared across the team.
Steps
1. Read current config
cat ~/.claude/brain/config.json
If team is already configured, show current settings and ask:
"Team vault already configured. What would you like to do?
- Update settings
- Re-clone or reinitialize vault
- Disable team mode
- Exit"
2. Team vault configuration
Team name:
"Short team name (e.g.
fiale-plus, used for identification):"
Team vault path:
"Team vault path? Default:
~/brain-team"
Create team repo on GitHub:
After team name is entered, suggest a naming convention and offer to create the repo:
"For a dedicated team brain repo, the convention is:
<org>/<org>-brain(e.g.,fiale-plus/fiale-plus-brain)<org>/<team>-brain(e.g.,acme/platform-brain)Create it now? [Y/n] (requires
ghCLI + appropriate GitHub permissions)"
If Y and gh is available:
- Ask: "Repo name? (e.g.,
fiale-plus/fiale-plus-brain)" — pre-fill with<team_name>/<team_name>-brain - Run:
gh repo create <name> --private --description "Team knowledge vault" - Use the returned clone URL as the git remote (skip the manual URL prompt below)
If N or gh not available:
- Continue to the manual URL prompt
Git remote URL:
"Git remote URL? (blank = local-only, no remote sharing)"
Skip this prompt if the GitHub repo was just created above.
Team repos for auto-routing:
Ask:
"How do you want to specify which repos route knowledge to the team vault?
- Org folder — all repos under a directory (with optional exclude list) [default]
- Discover — scan a folder and pick specific repos"
If option 1 (org folder):
- Ask: "Folder path? (e.g.
~/repos/fiale-plus/)" - Run:
find <folder> -maxdepth 1 -mindepth 1 -type d | sortand show discovered git repos (informational) - Store as
project_paths: ["<expanded_path>"]in config
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 · 184 lines · 17 tokens per session scan B b3eeb0e7d42f
brain-team-setup 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 1,610 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.