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 wahidyankf/ose-public --skill plan-creating-project-plansgit 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/skills/wahidyankf/ose-public/plan-creating-project-plans)<a href="https://agentmods.dev/skills/wahidyankf/ose-public/plan-creating-project-plans"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/plan-creating-project-plans/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/wahidyankf/ose-public/plan-creating-project-plans"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/plan-creating-project-plans.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.00050 | $0.01736 |
| Opus 5.5 | $0.00020 | $0.00694 |
| Sonnet 5.5 | $0.00010 | $0.00347 |
| Haiku 4.5 | $0.00005 | $0.00174 |
Grade A, and why
plan-creating-project-plans 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Project Plans
Purpose
This Skill provides guidance for creating structured project plans in the plans/ directory. Plans follow standardized organization, naming conventions, and acceptance criteria patterns for executable, traceable project work.
When to use this Skill:
- Creating new project plans
- Organizing backlog items
- Converting ideas to structured plans
- Writing Gherkin acceptance criteria
- Structuring multi-phase projects
- Moving plans through workflow stages
Authorization gate: creating a tracked plan requires a literal user plan request or explicit
plan-authoring invocation. Plan Mode, internal task planning, discovery, and omitted tester output
mode do not authorize plans/ writes. The standing exception is the
Upstream Tool Defects
standard's two-pager or
Bug-Fix Plan — the latter
one README.md whose sections take the core documents' roles.
Start here — mandatory grilling: before writing, resolve material design decisions that cannot be answered from repository evidence. After writing, run a separate validation/stress-test grill against the completed artifacts before signaling done. See mandatory-grilling.md.
Minimal Sufficiency in Plans
Treat the requested outcome, explicit non-goals and out-of-scope items, acceptance criteria, and required quality gates as the plan's boundary and stop condition. When a plan introduces code, a dependency, abstraction, validator, automation, infrastructure, or another lasting mechanism, the chosen technical form must name its concrete need and explain why existing mechanisms are insufficient. Choose the smallest responsible design that satisfies every applicable rule; mandatory safeguards remain part of sufficiency. See Plans Best Practices.
What ships with it
26 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- README.md 458 B
- reference/common-mistakes.md 2.0 KB
- reference/delivery-mode.md 3.2 KB
- reference/delivery-plan-tdd-structure.md 2.4 KB
- reference/execution-grade-clarity.md 4.2 KB
- reference/executor-tagging.md 3.3 KB
- reference/gherkin-acceptance-criteria.md 1.8 KB
- reference/knowledge-capture-phase-template.md 3.9 KB
- reference/knowledge-capture-scaffold-and-entries.md 1.8 KB
- reference/mandatory-grilling.md 4.3 KB
- reference/manual-ui-and-api-verification.md 4.1 KB
- reference/manual-verification-retest-rules.md 1.8 KB
- reference/mermaid-diagrams.md 1.3 KB
- reference/operational-readiness.md 3.7 KB
- reference/phases-as-natural-pauses.md 1.5 KB
- reference/plan-archival.md 4.8 KB
- reference/plan-folder-and-naming.md 1.6 KB
- reference/plan-lifecycle-and-git-workflow.md 2.8 KB
- reference/plan-structure-multi-and-single-file.md 4.6 KB
- reference/README.md 3.5 KB
- reference/refuse-uncertainty-and-anti-patterns.md 2.2 KB
- reference/specialized-executor-annotation.md 2.0 KB
- reference/ui-design-funnel-grilling-and-learning-plans.md 2.9 KB
- reference/ui-design-funnel.md 3.7 KB
- reference/verification-recipes.md 3.2 KB
- reference/worktree-specification.md 4.4 KB
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 Changed · +1 lines 744e777a9951
- 2d ago First seen · 113 lines · 50 tokens per session scan A f11e6d5949f6
plan-creating-project-plans is a skill published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 1,736 once invoked, about $0.0002 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 skills, from other repositories
add-a-lib
Scaffold a new shared library under libs/ in the builders-stack monorepo. Use when code is needed in two or more places (apps or services) and should become a single source of truth consumed by package name. Covers the package.json, tsconfig, the one-public-door src/index.ts barrel, and wiring it into a consumer…
implement
Implement an agreed issue or spec through implementation, review, fixes, and a PR ready to merge.
triage
Classify an issue, identify missing information, and decide whether bounded automatic work is safe.
record-gotchas
Capture surprises, workarounds, and rough edges hit while consuming the public surface of Prisma 8, Prisma Compute, or Prisma Postgres — anything a real user of these products would experience. Fires whenever an operator (or agent) writes a workaround, hits a surprising failure mode, or finds undocumented behaviour…
resolution_playbook
How to choose one resolution action from a ticket and its customer history.
stacking-prs
Create and manage GitHub native Stacked PRs in this repo with the gh stack CLI. Use when asked to stack PRs, split a large change into a stack, add a layer to a stack, restack or rebase a stack, adopt existing branches or PRs into a stack, check out someone else's stack, or land a stack. Covers creating and submitting…