A command for managing a private team identity for one repository. The team is represented by a secret, so members can share presence information such as who is online and what they are editing.

Use it to create a team, join one using a shared secret, switch teams, or inspect the repository's current team.

It keeps presence information separated between teams and repositories. Developers can work alone by default, then deliberately create or join a shared team.

team — Command by randomittin

Install

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.

agentmods

npx agentmods add commands/randomittin/heimdall/team

Clone the repo

git clone --depth 1 https://github.com/randomittin/heimdall

Per session 171 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,076 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00171	$0.01076
Opus 5	$0.00086	$0.00538
Sonnet 5	$0.00034	$0.00215
Haiku 4.5	$0.00017	$0.00108

Measured 2d ago against content hash e17ae19272ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

team scanned grade A with 1 finding 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 2d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

→ relay the printed team_id + the `curl … | … HEIMDALL_TEAM_SECRET='…' bash` join

commands/team.md · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/hmd:team — Manage This Repo's Team (Multi-Tenant Presence)

Use when a dev wants to control which TEAM this repo's presence is scoped to. A team = a secret scoped to a repo: a teammate's HAID, online state, and current file/edits are visible ONLY to holders of that secret; cross-team and outsiders see NOTHING. The secret's non-secret handle is team_id = sha256("heimdall-team\0"+secret)[:32] — the partition the server keys presence on.

Zero-config still holds: a dev does NOT have to run this. bin/heimdall-presence auto-mints a private solo team on the first beat/roster, so a new dev starts in their own team (sees only themselves) until they deliberately share or join.

Process

Mint a new team — new writes a fresh secret to <repo>/.heimdall/team.json (0600, gitignored) and prints the secret plus the heimdall-invite join one-liner to share:
```
"${CLAUDE_PLUGIN_ROOT}/bin/heimdall-team" new
```
It REFUSES to overwrite an existing team without --force (re-minting orphans you from the current team). Re-mint deliberately with:
```
"${CLAUDE_PLUGIN_ROOT}/bin/heimdall-team" new --force
```
Join a teammate's team — paste the secret they shared:
```
"${CLAUDE_PLUGIN_ROOT}/bin/heimdall-team" join '<team-secret>'
```
A secret shorter than 32 chars is rejected (a weak secret could collide into another team). This switches THIS repo onto their team on the next beat/roster.

Inspect the team — show prints the NON-SECRET team_id + whether configured; it NEVER prints the secret:

"${CLAUDE_PLUGIN_ROOT}/bin/heimdall-team" show
"${CLAUDE_PLUGIN_ROOT}/bin/heimdall-team" show --json

Recruit teammates — once a team exists, /hmd:invite (or bin/heimdall-invite) prints the one-command join carrying the team secret.

Constraints

The team secret is a secret. It is written ONLY to <repo>/.heimdall/team.json (mode 0600, gitignored) and never crosses another command's argv, a log, or a tracked file. new prints it to stdout ONCE (with a ⚠ caveat) so the owner can share it; show never prints it. When relaying new/invite output, keep the caveat attached and only share the secret with intended teammates.
One active team per repo. team.json holds one team; join switches teams by overwriting it. A dev on different repos may be on different teams.
The secret rides the wire ONCE, at enroll. heimdall-presence sends it in the X-Heimdall-Team-Secret header on /enroll; signed beats and roster reads thereafter carry NO secret (membership is server-side).
Don't hand-craft a secret. Use new (mints 43-char base64url, 256-bit entropy). Never type a short or low-entropy secret.

Read the full file on GitHub · 83 lines

Changes

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.

2d ago First seen · 83 lines · 171 tokens per session scan A e17ae19272ff

Subscribe to this mod's changes

team is a command published in the GitHub repository randomittin/heimdall (5 stars, last pushed 11d ago), licensed MIT. It adds 171 tokens to every session and 1,076 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code review Security ai-coding anthropic claude-code claude-plugin cli developer-tools

team

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Makes network callslowCapability

How it starts

/hmd:team — Manage This Repo's Team (Multi-Tenant Presence)

Process

Constraints

What this file has done since we first saw it

Other commands, from other repositories

autocode

autocode-new

dispatcher

standup

dev-planner

iterate