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-grooming-idea-briefsgit 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-grooming-idea-briefs)<a href="https://agentmods.dev/skills/wahidyankf/ose-public/plan-grooming-idea-briefs"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/plan-grooming-idea-briefs/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-grooming-idea-briefs"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/plan-grooming-idea-briefs.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.00069 | $0.00884 |
| Opus 5.5 | $0.00028 | $0.00354 |
| Sonnet 5.5 | $0.00014 | $0.00177 |
| Haiku 4.5 | $0.00007 | $0.00088 |
Grade A, and why
plan-grooming-idea-briefs 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grooming Idea Briefs
Purpose
This Skill is the invocable entry point for the
plan-ideas-grooming workflow.
That workflow declares Execution Mode: Direct Orchestration and states that "the procedure lives
entirely in this workflow document" — meaning the calling context performs the steps itself and
there is no delegated agent behind it. This Skill exists so that running the workflow is a named,
callable action rather than an undifferentiated sequence of file edits: invoking it loads the
procedure below, and the run is attributable.
Read the workflow document for the full normative text. This Skill carries the operational essentials and the traps; it does not restate all ten steps verbatim.
When to use this Skill
- A repo's
plans/ideas/(summed across quadrant folders, excludingREADME.md) exceeds 60 flat idea files. - 90 days have elapsed since the
> Last groomed: YYYY-MM-DDline in that repo'splans/ideas/README.md. - A maintainer explicitly asks for idea grooming across one or more repos.
Do not use it to file a new idea (write the two-pager directly) or to promote a ripe idea into a
backlog plan (that is plan-planning, following the Plans convention's promotion steps).
Inputs
| Input | Required | Default | Notes |
|---|---|---|---|
repos |
yes | none | Comma-separated repo paths. Supply every repo in one run — Steps 3-4 are cross-repo. |
dry-run |
no | false |
Compute and log every decision without writing. |
delivery-mode |
no | worktree-to-pr |
Fixed, no override — write scope below is never infra-as-code. |
What ships with it
4 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.
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 · 66 lines · 69 tokens per session scan A c6581631fe52
plan-grooming-idea-briefs is a skill published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 884 once invoked, about $0.0003 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…