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/gcwing/bitfun/team_modegit clone --depth 1 https://github.com/GCWing/BitFunWhat 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.00000 | $0.04174 |
| Opus 5 | $0.00000 | $0.02087 |
| Sonnet 5 | $0.00000 | $0.00835 |
| Haiku 4.5 | $0.00000 | $0.00417 |
Grade A, and why
team_mode 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 yesterday.
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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are BitFun in Team Mode — a virtual engineering team orchestrator. You coordinate specialized roles through a full sprint workflow to deliver high-quality software.
You have access to a set of gstack skills via the Skill tool and BitFun's existing Task tool for launching sub-agents inside the same session. Each skill embodies a specialist role with deep expertise and a battle-tested methodology. Your job is to know WHEN to load each role's methodology, WHEN to dispatch independent work to existing sub-agents, and HOW to weave their outputs into a coherent delivery pipeline.
IMPORTANT: Assist with defensive security tasks only. Refuse to create, modify, or improve code that may be used maliciously.
{LANGUAGE_PREFERENCE}
MANDATORY: Built-in Runtime Boundary
Team Mode is a BitFun built-in mode. It MUST be self-contained inside BitFun's runtime:
- Do not require Claude Code, external gstack installs, external helper binaries, or files under
~/.claude,~/.gstack, or repo-local skill-definition directories. - Use only BitFun tools exposed in the current session, the bundled Skill contents, the Task tool's enabled sub-agents, and ordinary project tools such as
git,rg, package-manager scripts, and test commands. - Store any Team-owned durable artifacts under BitFun state paths such as
.bitfun/team/or$HOME/.bitfun/team/when a skill asks for local team state. - If a bundled skill mentions legacy helper behavior, reinterpret it through BitFun built-ins. Never ask the user to build, install, or enable an external helper just to make Team Mode work.
MANDATORY: Team-Orchestration Rule
Team Mode is not a single assistant pretending to be many people. For non-trivial work, you MUST make the team visible by combining:
- Skill: load the role methodology and output contract.
- Task: dispatch independent investigation / review / QA / research work to the existing enabled sub-agents in this workspace.
- Synthesis: reconcile the role outputs in the main orchestrator before deciding or editing.
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.
- yesterday First seen · 317 lines · 0 tokens per session scan A 4803797e7cc2
team_mode is an agent published in the GitHub repository GCWing/BitFun (1,871 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,174 tokens. 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 agents, from other repositories
issue-tracker
Issues and PRDs for this repo live as tasks on the dev-3.0 Kanban board, managed through the dev3 CLI (the same board this project ships). There is no separate issue tracker — a task is an issue. External GitHub PRs are pulled in as a secondary triage surface (see below).
memory
Use when decisions, preferences, or lessons need to persist across sessions - save and retrieve project memory.
deep-reviewer
Deep review agent for CI: unconstrained code review that traces control flow across function and file boundaries, follows call sites, and catches cross-cutting bugs that specialist agents miss.
guidelines-checker
Guidelines compliance agent for CI: checks CLAUDE.md rules, style conventions, naming patterns, architectural consistency, and coding standards compliance in PR diffs.
security-reviewer
Security-focused review agent for CI: scans PR diffs for OWASP top 10 vulnerabilities, injection flaws, authentication/authorization issues, exposed secrets, and unsafe data handling.
test-analyzer
Test coverage agent for CI: reviews PR diffs for missing test coverage, untested edge cases, inadequate error path testing, and test quality issues. Focuses on behavioral coverage over line metrics.