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 agentmods add skills/andyduck-ops/omp-flow/omp-flow-brainstormnpx skills add Andyduck-ops/omp-flow --skill omp-flow-brainstormgit clone --depth 1 https://github.com/Andyduck-ops/omp-flowWrote 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/andyduck-ops/omp-flow/omp-flow-brainstorm)<a href="https://agentmods.dev/skills/andyduck-ops/omp-flow/omp-flow-brainstorm"><img src="https://agentmods.dev/badge/skills/andyduck-ops/omp-flow/omp-flow-brainstorm.svg" alt="Measured on agentmods" 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 | $0.00035 | $0.00882 |
| Opus 5 | $0.00017 | $0.00441 |
| Sonnet 5 | $0.00007 | $0.00176 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
omp-flow-brainstorm 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 4d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OMP-Flow Brainstorm
Preconditions
- The user consented to task creation or selected an existing task.
- The active task is a readable Bundle with a root index.
- The assignment identifies the Bundle root, bounded objective, entry Concept, and allowed output.
- The entry normally points to
brainstorm.mdor a linked framing Concept.
First-Principles Orientation
For a non-trivial Explore, use repository/Wiki evidence and human calibration to form or revise a provisional first-principles anchor(第一性锚定)before broad Research. Keep it in useful authored prose, not a required file or fixed checklist. It should be sufficient to expose the concrete actors and action, observable intended outcome, current principal contradiction(主要矛盾), irreducible outcome, human boundaries, a strong counter-hypothesis, and evidence that would revise the framing. Mechanical low-ambiguity work may proceed directly when this would not improve a decision.
Concentrate interaction on the material decision frontier:
- For purpose, values, risk tolerance, and non-negotiable outcomes, the human states a position first; then give the strongest counter-case, counterexample, and consequence.
- For evidence-led technical choices, an Agent may lead with a recommendation only when it also gives the strongest counter-case and a falsifier: the evidence that would overturn it.
- Use targeted high-intensity Grill only while a question can change the problem core or outcome. Do not exhaust branches, prescribe a question count, or let the Agent silently rank human values.
Interview Contract
- Read the entry Concept and follow only useful links from the Bundle.
- Record the initial request, concrete actors/action/outcome, current principal contradiction, and known repository facts in the assigned framing Concept.
- Inspect code, tests, docs, prior tasks, relevant history, and applicable durable knowledge
through the native
omp-flow-wikiSkill before asking repository-answerable questions. - Ask the user one material decision question at a time. Ask only about purpose, value, risk tolerance, preference, or use that repository and other relevant practice evidence cannot establish.
- Keep confirmed facts, assumptions, disagreements, alternatives, constraints, success criteria, and open questions distinct.
- Present materially different directions only when a real choice exists. Follow the human-first and recommendation/counter-case order above instead of anchoring value choices with a model default.
- Update the linked framing Concept as decisions change. Chat is not the durable source.
- When a question needs evidence, link a bounded research Concept or assignment and state what anchor assumption, contradiction, or practical decision the result may change. When research confirms, revises, or falsifies the framing, update the authored anchor and next question. This is a practice test(实践检验)spiral, not a one-way gate.
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.
- 4d ago First seen · 79 lines · 35 tokens per session scan A 883c25302b37
omp-flow-brainstorm is a skill published in the GitHub repository Andyduck-ops/omp-flow (6 stars, last pushed 8d ago), licensed MIT. It adds 35 tokens to every session and 882 once invoked, about $0.0002 per session on Opus 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…