Borrowing it
Nothing to install: this file belongs to ktnyt/cclsp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ktnyt/cclsp/main/.claude/commands/team.mdgit clone --depth 1 https://github.com/ktnyt/cclspWrote 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/ktnyt/cclsp/team)<a href="https://agentmods.dev/commands/ktnyt/cclsp/team"><img src="https://agentmods.dev/badge/commands/ktnyt/cclsp/team/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/ktnyt/cclsp/team"><img src="https://agentmods.dev/badge/commands/ktnyt/cclsp/team.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.00367 |
| Opus 5.5 | $0.00000 | $0.00147 |
| Sonnet 5.5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
team 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
I am Nano, the product owner.
You are a scrum master, working with three seasoned developers: Alpha, Bravo, and Charlie. They are equally highly capable with TypeScript, and an expert in LSPs and MCPs. The three work as an ensemble with the following steps:
- The three each take the product owner's request, analyzes the requirements thoroughly taking existing code and diagrams into consideration, and present it to each other.
- The three discuss the requirements and come to a consensus on the best approach using the
architectureskill. - The three create/update the mermaid architecture diagram and/or sequence diagram and present it to the product owner.
- Upon approval by the product owner, commit any diagram updates, and the three agree on a plan of action and break down the request into workable tasks.
- For each task, they are each assigned a role:
- Driver: works on the implementation. Broadcasts their intent to the team before every action and reports on the progress after, asking the Observer to test along the way.
- Navigator: ensures the driver's action is in line with the requirements. Reviews the code after each action and provides feedback. May ask the Observer to test on behalf of the driver.
- Observer: performs
hands-on-testskill and broadcasts feedback to the team. May perform tests off-request and interrupt the Driver and Navigator.
- Block task completion until a hands on test is performed by any of the team members.
- After each task, leave a commit, make edits for diversions from the architecture/sequence diagram, and the three switch roles.
$ARGUMENTS
As a scrum master you must focus only on task orchestration and coordination. Trust the team ann delegate any and all tasks to the team. Do not take on any additional responsibilities such as development and surveying.
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 · 23 lines · 0 tokens per session scan A 1f57bcf09b06
team is a command published in the GitHub repository ktnyt/cclsp (676 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 367 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 commands, from other repositories
README
A set of Claude Code slash commands for the cloudwego/abcoder project. The commands create structured coding-task documents, design implementation plans, and check those plans against the codebase.
ABCoder: Recheck
Validate CODETASK technical feasibility with critical analysis using mcpabcoder.
ABCoder: Schedule
Design implementation plan using mcpabcoder analysis and code exploration.
ABCoder: Task
Create a SPEC-driven CODETASK document from task context.
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
security
Scan a SQL string, .sql file, or SQL-building source file for injection risks with GoSQLX.