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.
git clone --depth 1 https://github.com/bluzername/claude-code-power-stackWrote 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/bluzername/claude-code-power-stack/team-log)<a href="https://agentmods.dev/commands/bluzername/claude-code-power-stack/team-log"><img src="https://agentmods.dev/badge/commands/bluzername/claude-code-power-stack/team-log/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/bluzername/claude-code-power-stack/team-log"><img src="https://agentmods.dev/badge/commands/bluzername/claude-code-power-stack/team-log.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00249 |
| Opus 5.5 | $0.00000 | $0.00100 |
| Sonnet 5.5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
team-log 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 1mo 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
/team-log - Log a decision, finding, or blocker for your team
Append an entry to the team's shared log (.team/log.jsonl in the project directory).
Steps
1. Check team mode is initialized
Run: ls .team/log.jsonl
If it doesn't exist, run: ccs team init
2. Determine the entry type from the user's message
| Type | When to use |
|---|---|
decision |
A technical or design choice was made |
finding |
Something was discovered during research or debugging |
blocker |
Something is blocking progress |
done |
A phase, feature, or task was completed |
handoff |
Work is being passed to a teammate |
Default to decision if unclear.
3. Log it
Run this command, replacing TYPE and MESSAGE:
ccs team log TYPE "MESSAGE"
The entry automatically includes your name (from git config user.name) and timestamp.
4. Remind about git
After logging, remind the user: "Don't forget to commit and push .team/log.jsonl so your team sees this."
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.
- 1mo ago First seen · 37 lines · 0 tokens per session scan A ad720287b160
team-log is a command published in the GitHub repository bluzername/claude-code-power-stack (2 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 249 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-31.
Other commands, from other repositories
speckit.companion.implement
Companion implement — execute tasks.md in dependency order, then mark complete.
workflow-design
Exécuter la phase de Conception (Solutioning) - spécification technique et architecture.
sprint
Équipe de Développement Sprint - Implémentation parallèle de stories utilisant les Agent Teams.
speckit.companion.living-move
Move a living spec between central and colocated storage — file, tiers, and registry together (opt-in, reversible).
daily-standup
Génération Résumé Daily Stand-up.
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.