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/cluesmith/codevWrote 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/cluesmith/codev/team)<a href="https://agentmods.dev/commands/cluesmith/codev/team"><img src="https://agentmods.dev/badge/commands/cluesmith/codev/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/cluesmith/codev/team"><img src="https://agentmods.dev/badge/commands/cluesmith/codev/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.00896 |
| Opus 5.5 | $0.00000 | $0.00358 |
| Sonnet 5.5 | $0.00000 | $0.00179 |
| Haiku 4.5 | $0.00000 | $0.00090 |
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.
How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
team - Team Coordination CLI
The team command manages team members and messages for your Codev project. Team data is stored in codev/team/ and displayed in the Tower dashboard.
Synopsis
team <command> [options]
Commands
team list
List all team members from codev/team/people/.
team list
Output is a formatted table:
Name GitHub Role
──────────────── ────────────── ──────────────
M Waleed Kadous waleedkadous Lead Architect
Jane Doe jdoe Developer
Warns if fewer than 2 members (Team tab requires 2+).
team message <text>
Post a message to codev/team/messages.md.
team message "Spec 42 is ready for review"
team message "Deployed to staging" -a deploy-bot
Options:
| Flag | Description |
|---|---|
-a, --author <name> |
Override author (default: auto-detect from gh CLI or git config) |
Creates messages.md with header if it doesn't exist. Messages are append-only.
team update
Post an hourly activity summary. Usually called by cron.
team update
Collects notable events from the last hour:
- Builder spawns (from git log)
- Gate approvals (from status.yaml)
- PR merges (from
ghCLI) - Completed reviews (from codev/reviews/)
Posts a summary via team message. Exits silently if no events.
team add <github-handle>
Scaffold a new team member file.
team add waleedkadous
team add jdoe --name "Jane Doe" --role "Developer"
Options:
| Flag | Description |
|---|---|
-n, --name <name> |
Full name (default: github handle) |
-r, --role <role> |
Role (default: "Team Member") |
Creates codev/team/people/<handle>.md. Handle is normalized to lowercase. Validates GitHub handle format. Fails if member already exists.
Team Directory
codev/team/
├── people/ # One .md file per member
│ ├── waleedkadous.md
│ └── jdoe.md
└── messages.md # Append-only message log
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 · 153 lines · 0 tokens per session scan A bdae3a5f0fb7
team is a command published in the GitHub repository cluesmith/codev (289 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 896 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
feedback
A command for collecting user feedback and turning it into a GitHub issue, a tracked item in the GitHub code-hosting service.
todo
Compatibility alias for the canonical GTD task-management entry point.
gtd
Canonical GTD entry point for capture, clarification, organization, review, and engagement.
next-issue
Fetch the next ready-for-agent issue by priority.
tasks-to-ado
Convert existing tasks into actionable, dependency-ordered Azure DevOps work items for the feature based on available design artifacts.
tasks-to-issues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.