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/allisoneer/agentic_auxilaryWrote 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/allisoneer/agentic_auxilary/create_plan_final)<a href="https://agentmods.dev/commands/allisoneer/agentic_auxilary/create_plan_final"><img src="https://agentmods.dev/badge/commands/allisoneer/agentic_auxilary/create_plan_final/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/allisoneer/agentic_auxilary/create_plan_final"><img src="https://agentmods.dev/badge/commands/allisoneer/agentic_auxilary/create_plan_final.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.00019 | $0.01310 |
| Opus 5.5 | $0.00008 | $0.00524 |
| Sonnet 5.5 | $0.00004 | $0.00262 |
| Haiku 4.5 | $0.00002 | $0.00131 |
Grade A, and why
create_plan_final 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.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<workflow_contract>
- Follow all 5 steps in order.
- Treat any additional instructions in
<userMessage>as requirements for this finalization pass. - Use
todowriteto track dossier writing, gap resolution, plan generation, review, and persistence. - Do not generate the final implementation plan while critical questions remain unresolved.
- Before persisting the final plan, present a concise summary and ask for user feedback.
- Keep the requirements dossier and implementation plan paired under the same readable base name. </workflow_contract>
MAKE SURE you follow ALL 5 steps in order. Track your progress with todowrite throughout.
<step_1>
Step 1: Write the Requirements Dossier
- Read every file, research artifact, prior plan artifact, or other document referenced in
<userMessage>fully. - Treat any extra user instructions in
<userMessage>as input that may refine or override the Phase 1 outcome. - If ANY content appears in
<userMessage>, take it into account. This is important. - Call
tools_thoughts_get_templatewithtemplate=requirements. - Consolidate the Phase 1 findings, user decisions, constraints, and unresolved caveats into a formal requirements dossier.
- Write the dossier with
tools_thoughts_write_documentusing:doc_type: "plan"filename: {readable_descriptive_name}_requirements.md(use onlyA-Za-z0-9._-, no slashes)content:the completed dossier following the requirements template
- This dossier becomes the formal record of Phase 1 decisions and will be passed directly to the reasoning model in Step 3.
- Store the returned dossier path for the remaining steps.
</step_1>
<step_2>
Step 2: Preflight for Remaining Gaps
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 · 134 lines · 19 tokens per session scan A 3622d26ee910
create_plan_final is a command published in the GitHub repository allisoneer/agentic_auxilary (79 stars, last pushed 6d ago), licensed MIT. It adds 19 tokens to every session and 1,310 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-08.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
sync-linear
Sync current work with Linear ticket status.
plc-project-status
Read .claude/skills/plc-project-status/SKILL.md and execute its official procedure. Target: $ARGUMENTS.