claude-agent-team
CLAUDE.md8 starsChanged 31 days agoMITView on GitHub
Requires clean working tree (tracked and untracked) in every deploy-source path (GUARD_PATHS in install.sh: agents/, commands/, skills/, rules-core/, scripts/, bin/, config/, managed-settings.d/, macos/, tools/justfile, cast/, VERSION, plus the --personal overlay dirs) — install aborts on uncommitted changes, and also outside a git work tree. Bypass with CAST_INSTALL_FORCE=1 (CI only). HARD RULE: Run only against an isolated temp HOME, never against real ~/.claude. The suite's teardown deletes its HOME-scoped fixtures, so it must run only against an isolated temp HOME —…
- Reads credentials
In this repository21 other files it gives its agents.
- commands/agents.mdAGENTS.md
- rules-core/agents.mdAGENTS.md
- agent-registrySkill
- briefing-writerSkill
- careful-modeSkill
- cast-auditSkill
- cast-conventionsSkill
- deep-researchSkill
- freeze-modeSkill
- git-activitySkill
- laconicSkill
- mergeSkill
- orchestrateSkill
- planSkill
- python-conventionsSkill
- seo-checklistSkill
- seo-index-censusSkill
- shipSkill
- stack-referenceSkill
- typescript-conventionsSkill
- wizardSkill
The file
We split this CLAUDE.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
HARD RULE: Run only against an isolated temp HOME, never against real ~/.claude.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
claude-agent-team (CAST)
Install
bash install.shRequires clean working tree (tracked and untracked) in every deploy-source path (GUARD_PATHS in install.sh: agents/, commands/, skills/, rules-core/, scripts/, bin/, config/, managed-settings.d/, macos/, tools/justfile, cast/, VERSION, plus the --personal overlay dirs) — install aborts on uncommitted changes, and also outside a git work tree. Bypass with CAST_INSTALL_FORCE=1 (CI only).
Test
bash tests/run.sh # Run the full BATS suite (isolated temp HOME)
make ci-local # Run real GitHub Actions CI locally via actHARD RULE: Run only against an isolated temp HOME, never against real ~/.claude. The suite's teardown deletes its HOME-scoped fixtures, so it must run only against an isolated temp HOME — never your real ~/.claude. Use the setup_temp_home / teardown_temp_home helpers in tests/helpers/setup.bash.
tests/test_helper/bats-support and tests/test_helper/bats-assert are git submodules — on a fresh clone, run git submodule update --init --recursive first or tests/run.sh will refuse to start.
The make ci-local target (also: cast ci-local) runs hook-contract-validation (scripts/cast-validate-all-hooks.sh --source) and python-unit (python3 -m unittest discover -s tests -p 'test_*.py' -v) directly, BEFORE the act loop, then runs the remaining 8 PR-gating workflows (bats, stats-guard, rules-drift, readme-structure, pii-scan, shellcheck, db-contract, self-lints) via act. Requires act and Docker. Dropped from the act loop: contract-test (advisory-only by construction — || true + continue-on-error: true in bats-ci.yml, provides no enforcement signal); hook-contract-validation (real gate, run directly and BEFORE the loop so a later act-job failure can't silently skip it — it declares needs: bats, so under act it re-ran the full BATS suite as a dependency); and python-unit (PyYAML is absent from the act image catthehacker/ubuntu:act-latest but present on GitHub's ubuntu-latest, so it fails under act for a reason unrelated to real regressions — run directly as the workflow's exact command instead). Excluded from act: gitleaks (needs live GITHUB_TOKEN), bats-macos (no macOS runner in act), bats-ubuntu (duplicates bats).
Run
cast status # health check after installNon-obvious
agents/core/holds the 27 canonical agent definitions — edit there, then reinstall..claude/at repo root is a runtime install artifact (output ofinstall.sh), not a config location for development.CAST_DB_PATHoverrides the default SQLite path (~/.claude/cast.db).CAST_COMMIT_AGENT=1escape-hatch prefix allows rawgit commitwhen the commit agent is unavailable.tools/justfileis the canonical source for thejust -g <recipe>cost/trend recipes;install.shdelivers it to~/.config/just/justfile. Unlike every other install step this one overwrites (backing up first, and aborting if the backup fails) — skip-if-exists is what previously meant a merged fix never reached the live file. Cost/trend recipes read theagent_runs_dailyrollup, so the CURRENT day is partial until the nightly rollup runs; each prints arollup_age.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

