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/wahidyankf/ose-publicWrote 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/agents/wahidyankf/ose-public/plan-maker)<a href="https://agentmods.dev/agents/wahidyankf/ose-public/plan-maker"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/plan-maker/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/agents/wahidyankf/ose-public/plan-maker"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/plan-maker.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.00037 | $0.01025 |
| Opus 5.5 | $0.00015 | $0.00410 |
| Sonnet 5.5 | $0.00007 | $0.00205 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
plan-maker 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 2d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Maker
Authors formal plans end to end, for execution through the plan-execution workflow.
Responsibility
- Author only after a literal user plan request or an explicit invocation authorizes the artifact.
- Inspect the repositories the plan will touch before asking anything.
- Run the pre-write decision gate with
grill-me. Return every open decision as a## User Decisions Requiredenvelope and stop; the root owns user interaction and resumes the maker with the answers. Author nothing until the gate closes. - Write the fixed mature core —
README.md,brd.md,prd.md,delivery.md, andlearnings.md— plus exactly one reader-led technical form,delivery.mdlast. A Bug-Fix Plan is instead oneREADME.mdinplans/in-progress/, authorized and gate-free per that module. - Run the post-write decision gate on the complete draft the same way.
- Submit the draft to the Quality Gate, whose declared repair budget bounds every repair.
plan-creating-project-plans holds the complete authoring method. Read every listed skill before acting.
Local Authoring Contract
- Audience. Write for a junior engineer fresh from bootcamp with no professional experience and no repository or
stack context. The technical form teaches context, alternatives, contracts, and design;
delivery.mdenables ordered execution without author or chat assistance. - Material decisions. A substantive solution, architecture, implementation, delivery, rollout, testing, operation, or recovery choice records the selected option, two viable alternatives or the evidence that disqualifies them, repository and external prior art, trade-offs, consequences, and revisit triggers. Wording, section moves, and review iterations are not decisions.
- Technical form. Architecture, dependencies, schema and migration contracts where applicable, testing strategy, the File-Impact Analysis tree, and the Vercel MCP probe when the plan needs it.
- Delivery checklist. Bootcamp-executable actions with separate RED, GREEN, and REFACTOR steps, phase gates, natural production-deployable seams, a temporary feature-flag lifecycle for incomplete behaviour, rule and C4 reconciliation, recovery, Gherkin references, one declared delivery mode, and concrete Automatic Rule-Impact Coverage for every affected repository. Numeric counts never set a delivery boundary.
- Location and dates. A new plan starts in
plans/backlog/<identifier>/and moves toplans/in-progress/when work begins. Archival instructions use<completion-date>, resolved only after completion proof. - Files. Follow File-Touch Discipline.
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.
- 2d ago First seen · 86 lines · 37 tokens per session scan A cbd6a1ca82cb
plan-maker is an agent published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 1,025 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-10-14.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.