ask

A two-stage method for exploring product features: first generating broad ideas, then narrowing them into an approved plan.

In plain words
What is it for?
Use it to analyze feature value, create an executive summary and wireframes, collect feedback, and plan implementation and quality checks.
Why use it?
It separates creative exploration from decision-making and requires human approval before detailed planning continues.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/wellapp-ai/well/ask
Clone the repo
git clone --depth 1 https://github.com/WellApp-ai/Well
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,047 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00008 $0.05047
Opus 5 $0.00004 $0.02524
Sonnet 5 $0.00002 $0.01009
Haiku 4.5 $0.00001 $0.00505

Measured 2d ago against content hash 273b58761ddf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ask 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.

cursor-rules/modes/ask.mdc · 590 lines

How it starts

The opening of the file, as written. The whole thing — 590 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Ask Mode (Value Analysis - Two-Phase Process)

For feature exploration, apply this two-phase methodology. Gate 1 requires human approval; Gate 2 reviews phasing.

┌─────────────────────────────────────────────────────────────┐
│  PHASE 1: DIVERGE — "Sell me your dream. Shoot the moon"    │
│  Skills: problem-framing, competitor-scan, design-context   │
│  ┌─────────────┐   ┌─────────────┐   ┌─────────────┐        │
│  │   Silent    │ → │  Executive  │ → │    Dream    │        │
│  │  Analysis   │   │   Summary   │   │  Wireframes │        │
│  └─────────────┘   └─────────────┘   └─────────────┘        │
│         ↓                                                   │
│  ┌─────────────┐   ┌─────────────┐                          │
│  │  Feedback   │ → │   GATE 1    │ ← Human: OK/KO/DIG       │
│  │   Request   │   │             │   (KO → decision-capture)│
│  └─────────────┘   └─────────────┘                          │
└─────────────────────────────────────────────────────────────┘
                          ↓
┌─────────────────────────────────────────────────────────────┐
│  PHASE 2: CONVERGE (Silent Skills → Visible Output)         │
│  Skills: state-machine, qa-planning, dependency-mapping,    │
│          gtm-alignment, phasing                             │
│  ┌─────────────┐   ┌─────────────┐   ┌─────────────┐        │
│  │  Run Skills │ → │ QA Contract │ → │  Phasing    │        │
│  │  (silent)   │   │ (G#N, AC#N) │   │  Timeline   │        │
│  └─────────────┘   └─────────────┘   └─────────────┘        │
│         ↓                                                   │
│  ┌─────────────┐   ┌─────────────┐                          │
│  │  Executive  │ → │   GATE 2    │ ← Human: phase review    │
│  │   Summary   │   │             │   (KO → decision-capture)│
│  └─────────────┘   └─────────────┘                          │
└─────────────────────────────────────────────────────────────┘
                          ↓
                     Plan Mode (Value Engineering)

Read the full file on GitHub · 590 lines

Changes

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.

  1. 2d ago First seen · 590 lines · 8 tokens per session scan A 273b58761ddf

Subscribe to this mod's changes

ask is a cursor rule published in the GitHub repository WellApp-ai/Well (341 stars, last pushed 25d ago), licensed MIT. It adds 8 tokens to every session and 5,047 once invoked, about $0.0000 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-30.