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/planner)<a href="https://agentmods.dev/commands/tenon-net/tenonadmin/planner"><img src="https://agentmods.dev/badge/commands/tenon-net/tenonadmin/planner/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/planner"><img src="https://agentmods.dev/badge/commands/tenon-net/tenonadmin/planner.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.00012 | $0.00729 |
| Opus 5.5 | $0.00005 | $0.00292 |
| Sonnet 5.5 | $0.00002 | $0.00146 |
| Haiku 4.5 | $0.00001 | $0.00073 |
Grade A, and why
planner 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
- Use outcome-first, execution-ready plans: define the desired result, success criteria, constraints, evidence, validation path, and stop condition.
- Keep planning updates short and direct; surface only decisions that materially change the plan.
- Treat newer user instructions as local overrides for the active planning branch while preserving unrelated acceptance criteria.
- Keep the plan grounded in repository evidence and make every proposed step actionable.
<execution_loop>
- Inspect the repository and classify the request before asking about code facts.
- Extract scope, constraints, dependencies, file references, failure behavior, and acceptance targets.
- Resolve only genuine preference or tradeoff questions; otherwise choose the smallest coherent path.
- Draft a right-sized plan with ordered steps, risks, mitigations, and direct verification commands.
- Check that referenced files exist and that the handoff can proceed without guessing; save the requested plan artifact.
Keep inspecting referenced code, tests, documentation, and other evidence until requirements, affected resources, validation commands, failure behavior, and material open questions are traceable.
</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 · 68 lines · 12 tokens per session scan A 3b3ced06acf5
planner is a command published in the GitHub repository Tenon-Net/TenonAdmin (41 stars, last pushed 14d ago), licensed Apache-2.0. It adds 12 tokens to every session and 729 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.
planner compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| plannerTenon-Net/TenonAdmin | Command | 41 | 14d ago | Apache-2.0 | A | 12 | Claude Code, Codex |
| OPSX: Exploremuthuishere/toolnexus | Command | 5 | yesterday | MIT | A | 18 | Claude Code |
| OPSX: Applymuthuishere/toolnexus | Command | 5 | yesterday | MIT | A | 15 | Claude Code |
| OPSX: Archivemuthuishere/toolnexus | Command | 5 | yesterday | MIT | A | 13 | Claude Code |
| OPSX: Proposemuthuishere/toolnexus | Command | 5 | yesterday | MIT | A | 21 | Claude Code |
| OPSX: Syncmuthuishere/toolnexus | Command | 5 | yesterday | MIT | A | 14 | Claude Code |
| stuckData-Wise/claude-plugins | Command | 7 | yesterday | MIT | A | 0 | Claude Code |