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.
/plugin marketplace add CronusL-1141/AI-companynpx agentmods add plugins/cronusl-1141/ai-company/plugingit clone --depth 1 https://github.com/CronusL-1141/AI-companyGrade A, and why
ai-team-os 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 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.
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
{
"name": "ai-team-os",
"version": "1.11.3",
"description": "AI Agent Team Operating System for Claude Code with 113 MCP tools (incl. 42 ecosystem research tools), 25 agent templates, 11 hooks / 15 lifecycle events. Persistent team management, structured meetings, task wall, real-time React dashboard, and Ecosystem Research Platform v2 (progressive 4-stage deep-review funnel: shallow auto-summary → on-demand architecture → debate-based finalist evaluation → reference/integrate marking, with project-customizable thresholds, append-only history snapshots, and Failed self-learning).",
"author": {
"name": "CronusL-1141",
"url": "https://github.com/CronusL-1141"
},
"homepage": "https://github.com/CronusL-1141/AI-company",
"repository": "https://github.com/CronusL-1141/AI-company",
"license": "MIT",
"mcpServers": "./.mcp.json"
}
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 14 lines scan A d0677dcb4016
ai-team-os is a plugin published in the GitHub repository CronusL-1141/AI-company (353 stars, last pushed 18d 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.
Other plugins, from other repositories
thoth
Dashboard-centric Agent Project OS for auditable AI execution, persistent project state, and human-visible workflow orchestration.
agt-governance
AGT governance hooks and MCP tools for Claude Code sessions.
hyperflow
Point it at a GitHub issue and get back a reviewed pull request. Hyperflow turns one AI coding session into a structured engineering pipeline: plan sharpens and decomposes the work, dispatch fans out parallel workers, and a domain specialist reviews every step — nothing ships unreviewed. 18 skills, 22 specialist…
agentlas-core-engine marketplace
Plugin marketplace listing 1 plugin: hephaestus.
kipi-dsse
DSSE issue workflow: scope-enforced edits, per-finding dispositions, Codex review gates. Provides /issue-start, /issue-approve, /issue-verify, /issue-review, /issue-amend, /issue-closeout. Consumes issue specs created by prd-os or dropped in manually.
claudeclaw
Persistent agent orchestrator for Claude Code. Multi-channel message routing, triage, and SWE task management. Run /claudeclaw:setup to create your first instance and configure channels.