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.
npx skills add Tenon-Net/TenonAdmin --skill plangit 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/skills/tenon-net/tenonadmin/plan)<a href="https://agentmods.dev/skills/tenon-net/tenonadmin/plan"><img src="https://agentmods.dev/badge/skills/tenon-net/tenonadmin/plan/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/skills/tenon-net/tenonadmin/plan"><img src="https://agentmods.dev/badge/skills/tenon-net/tenonadmin/plan.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.00026 | $0.00424 |
| Opus 5.5 | $0.00010 | $0.00170 |
| Sonnet 5.5 | $0.00005 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
plan 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.
What it actually says
Plan
Use $plan when the user asks for a plan or plan review. Clear implementation and focused fixes should execute directly. A request to skip planning leaves this skill and continues the requested work; it does not create an Ultragoal or another persistent workflow unless the user explicitly requests one.
Modes
| Mode | Trigger | Result |
|---|---|---|
| Direct | Detailed planning request or --direct |
Write the plan from repository evidence |
| Interview | --interview or a material unresolved decision |
Resolve the decision, then write the plan |
| Review | --review |
Return APPROVED, REVISE, or REJECT with actionable reasons |
Workflow
- Inspect the relevant repository facts before asking about codebase details.
- In interview mode, ask one focused question at a time and stop when the answer no longer changes the plan. In an attached OMX tmux runtime, use
omx question; outside tmux, use native structured input when available, otherwise ask one concise plain-text question. - Write the smallest plan that covers the requested outcome, affected files or components, testable acceptance criteria, implementation order, material risks, and verification.
- Cite concrete file paths and lines for consequential repository claims. Check that referenced files exist and that each acceptance criterion has an observable check.
- Save the result under
.omx/plans/unless the user requests another location.
For review mode, read the selected plan, test its claims against the repository, and explain every blocking gap. Use a specialist review only when it adds useful independent evidence.
Stop conditions
- Deliver the plan when remaining uncertainty does not change implementation or acceptance criteria.
- Escalate only a business or product trade-off that cannot be resolved from repository evidence or existing authorization.
- If the user says
continue, continue the current planning branch without restarting discovery.
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 · 33 lines · 26 tokens per session scan A beb97dc435de
plan is a skill published in the GitHub repository Tenon-Net/TenonAdmin (41 stars, last pushed 14d ago), licensed Apache-2.0. It adds 26 tokens to every session and 424 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-11-07.
plan compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| planTenon-Net/TenonAdmin | Skill | 41 | 14d ago | Apache-2.0 | A | 26 | Codex |
| community-research-insightclawdotnet/openclaw.net | Skill | 532 | yesterday | MIT | A | 41 | Claude Code, Codex |
| OpenSourceManagementdanielmiessler/LifeOS | Skill | 20k | yesterday | MIT | A | 212 | Claude Code, Codex |
| code-review-csharppnp/copilot-prompts | Skill | 902 | 3d ago | MIT | A | 66 | Claude Code, Codex |
| godot-code-reviewjame581/GodotPrompter | Skill | 929 | 5d ago | MIT | A | 67 | Claude Code |
| recipe-front-reviewshinpr/claude-code-workflows | Skill | 711 | 4d ago | MIT | A | 29 | Claude Code |
| om-build-workflowopen-mercato/open-mercato | Skill | 1.9k | yesterday | MIT | A | 63 | Claude Code, Codex |