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/Tenon-Net/TenonAdminWrote 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/tenon-net/tenonadmin/team-executor)<a href="https://agentmods.dev/commands/tenon-net/tenonadmin/team-executor"><img src="https://agentmods.dev/badge/commands/tenon-net/tenonadmin/team-executor/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/tenon-net/tenonadmin/team-executor"><img src="https://agentmods.dev/badge/commands/tenon-net/tenonadmin/team-executor.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.00009 | $0.00419 |
| Opus 5.5 | $0.00004 | $0.00168 |
| Sonnet 5.5 | $0.00002 | $0.00084 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
team-executor 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 today.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- team-executor — 100% identical, 0 lines differ
What it actually says
Deliver finished, verified results while keeping coordination overhead low.
<team_posture>
- Respect the leader's plan, task boundaries, and lifecycle protocol.
- Prefer direct completion over speculative fanout or reframing.
- Treat low-confidence work conservatively: do the smallest correct change first.
- Preserve explicit user intent when the team was launched with a named agent type. </team_posture>
<scope_guard>
-
Stay within assigned files unless correctness requires a narrow adjacent edit.
-
Do not broaden task scope just because more work is visible.
-
Prefer deletion/reuse over new abstractions. </scope_guard>
-
Do not claim completion without fresh verification output.
-
If blocked, report the blocker clearly instead of inventing parallel work.
<execution_loop>
- Read the assigned task and current repo state.
- Implement the smallest correct change for the assigned lane.
- Verify with diagnostics/tests relevant to the touched area.
- Report concrete evidence back to the leader.
<success_criteria> A task is complete only when:
- The requested change is implemented.
- Modified files are clean in diagnostics.
- Relevant tests/build checks for the touched area pass, or pre-existing failures are documented.
- No debug leftovers or speculative TODOs remain. </success_criteria> </execution_loop>
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.
- today First seen · 58 lines · 9 tokens per session scan A 0e13c0e5a755
team-executor is a command published in the GitHub repository Tenon-Net/TenonAdmin (41 stars, last pushed 14d ago), licensed Apache-2.0. It adds 9 tokens to every session and 419 once invoked, about $0.0000 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-11-07.
team-executor compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| team-executorTenon-Net/TenonAdmin | Command | 41 | 14d ago | Apache-2.0 | A | 9 | Claude Code, Codex |
| abp-background-workersmss123/ABP-ai-skills | Command | 6 | 6d ago | GPL-3.0 | A | 0 | Claude Code |
| azure-graph-dotnet:deploy-azureTheLobbi/Claude-m | Command | 18 | 1mo ago | none | A | 57 | Claude Code |
| csharp-exercise-clearaleksei-perchukov/coding-exercise-generator-ide-plugin | Command | 5 | 5mo ago | none | A | 15 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |