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/gotempsh/tempsWrote 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/gotempsh/temps/teams)<a href="https://agentmods.dev/commands/gotempsh/temps/teams"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/teams/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/gotempsh/temps/teams"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/teams.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.00926 |
| Opus 5.5 | $0.00000 | $0.00370 |
| Sonnet 5.5 | $0.00000 | $0.00185 |
| Haiku 4.5 | $0.00000 | $0.00093 |
Grade A, and why
teams 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
teams command reference
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
teams
Manage teams and project access
Subcommands:
list(ls) - List all teamscreate(add) - Create a new teamshow- Show a team with its members and projectsupdate- Update a team name or descriptiondelete(rm) - Delete a team (removes its members and project grants)members- Manage team membership
teams list (alias: ls)
List all teams
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--json |
Output in JSON format | - | No |
teams create (alias: add)
Create a new team
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
-n, --name <name> |
Team name | - | No |
-s, --slug <slug> |
URL-safe slug ([a-z0-9-]+) | - | No |
-d, --description <description> |
Team description | - | No |
--json |
Output in JSON format | - | No |
teams show
Show a team with its members and projects
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--json |
Output in JSON format | - | No |
teams update
Update a team name or description
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
-n, --name <name> |
New team name | - | No |
-d, --description <description> |
New description | - | No |
--json |
Output in JSON format | - | No |
teams delete (alias: rm)
Delete a team (removes its members and project grants)
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
-y, --yes |
Skip confirmation | - | No |
teams members
Manage team membership
Subcommands:
list(ls) - List a team's membersadd- Add a user to a teamset-role- Change a member's role in the teamremove(rm) - Remove a user from a team
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 · 130 lines · 0 tokens per session scan A 87f0afef82b3
teams is a command published in the GitHub repository gotempsh/temps (880 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 926 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-09-03.
Other commands, from other repositories
issue-prd-generation
You are generating a comprehensive Product Requirements Document (PRD) for a GitHub issue. This PRD will be passed to a separate AI agent instance with ONLY THIS CONTEXT for implementation. Write with that constraint in mind.
artifact-insight-scan
Analyze the provided project artifacts for missed insights, action items, and follow-ups that should become tracked issues.
start-development
Start the available Software Development Flow in Moira.
ccc-makeover
Score project health with X-Ray, apply the top recommendations in impact order with your OK for each, and show the before and after score. Use when you want the highest-impact project health fixes applied and measured.
signal-planner
Closed-loop autonomy — convert a production/analytics/incident signal into a dependency-ordered issue DAG, execute via /orchestrate, then verify the originating signal is resolved. Event-driven companion to /autopilot.
bootstrap
Bootstrap a new project with design system, CI/CD, i18n, SEO, and deploy pipeline.