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/openteams-lab/openteamsWrote 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/openteams-lab/openteams/setup)<a href="https://agentmods.dev/commands/openteams-lab/openteams/setup"><img src="https://agentmods.dev/badge/commands/openteams-lab/openteams/setup/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/openteams-lab/openteams/setup"><img src="https://agentmods.dev/badge/commands/openteams-lab/openteams/setup.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.00016 | $0.00460 |
| Opus 5.5 | $0.00006 | $0.00184 |
| Sonnet 5.5 | $0.00003 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
setup 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.
What it actually says
Connect Apps Setup
Set up the connect-apps plugin so Claude can take real actions in external apps (Gmail, Slack, GitHub, etc). Uses Composio for auth and app connections.
Instructions
Step 1: Ask for API Key
Ask the user for their Composio API key. If they don't have one, tell them to get a free key at: https://platform.composio.dev/?utm_source=Github&utm_content=AwesomeSkills
Just ask for the key directly. Don't ask if they have one first.
Step 2: Validate & Get MCP URL
Run this command (replace API_KEY_HERE with the actual key):
/opt/homebrew/bin/python3.11 -c "
from composio import Composio
composio = Composio(api_key='API_KEY_HERE')
session = composio.create(user_id='claude_user')
print(session.mcp.url)
"
If it fails with import error, first run: pip3 install composio
Step 3: Write Config
Write directly to ~/.mcp.json with this exact format:
{
"connect-apps": {
"type": "http",
"url": "THE_MCP_URL_FROM_STEP_2",
"headers": {
"x-api-key": "THE_API_KEY"
}
}
}
If ~/.mcp.json already exists with other servers, merge the "connect-apps" key into the existing JSON.
Step 4: Confirm
Tell the user:
Setup complete!
To activate: exit and run `claude` again
Then try: "Send me a test email at [email protected]"
Important
- Do NOT try to edit settings.local.json - MCP servers go in ~/.mcp.json
- Do NOT search for config locations - just write to ~/.mcp.json
- Do NOT ask multiple questions - just ask for the API key once
- Be fast - this should take under 30 seconds
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 · 68 lines · 16 tokens per session scan A 1741a0fcbd0a
setup is a command published in the GitHub repository openteams-lab/openteams (581 stars, last pushed 14d ago), licensed Apache-2.0. It adds 16 tokens to every session and 460 once invoked, about $0.0001 per session on Opus 5.5. 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
end-session
Wrap up the work session with read-only evidence gathering, owner-classified documentation handoffs, gated issue sync, Kano refinement, and git hygiene checks.
powershell-developer
Comprehensive PowerShell development assistance for scripts, modules, GUIs, and Windows automation with Microsoft best practices verification.
parallel-execution
Execute independent subtasks in parallel for maximum efficiency.
batch-executor
Parallel task execution specialist using batch operations.
trellis-finish-work
Wrap up the current session: archive the active task (and any other completed-but-unarchived tasks the user wants to clean up) and record the session journal. Code commits are NOT done here — those happen in workflow Phase 3.4 before you invoke this command.
cache-manage
Command "cache-manage" from spencermarx/open-code-review, covering cache-manage, usage, options, examples and view cache stats.