teamctl

A tool for managing persistent teams of AI agents defined in YAML, a text format for structured settings.

In plain words
What is it for?
Use it to declare, launch, and evolve a persistent team of AI agents through chat.
Why use it?
It guides setup from an uninstalled state to a running team and supports later changes to the team’s organisation.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add Alireza29675/teamctl
agentmods
npx agentmods add plugins/alireza29675/teamctl/claude-code
Clone the repo
git clone --depth 1 https://github.com/Alireza29675/teamctl

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

teamctl 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 yesterday.

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.

plugins/claude-code/.claude-plugin/plugin.json · 11 lines

What it actually says

{
  "name": "teamctl",
  "version": "0.3.0",
  "description": "Persistent AI agent teams, declared in YAML and launched from a chat with Claude. Walks you from no-teamctl-installed to a running team in one conversation, then stays useful for evolving the org afterwards.",
  "author": {
    "name": "teamctl",
    "url": "https://github.com/Alireza29675/teamctl"
  },
  "homepage": "https://github.com/Alireza29675/teamctl"
}
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.

  1. yesterday First seen · 11 lines scan A daca83bb4c0f

Subscribe to this mod's changes

teamctl is a plugin published in the GitHub repository Alireza29675/teamctl (20 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.