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 rules/brainy-builds/ts-inspect-cli/ask-megit clone --depth 1 https://github.com/Brainy-Builds/ts-inspect-cliWhat 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.02128 | $0.02128 |
| Opus 5 | $0.01064 | $0.01064 |
| Sonnet 5 | $0.00426 | $0.00426 |
| Haiku 4.5 | $0.00213 | $0.00213 |
Grade A, and why
ask-me 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ask Me
Purpose
What people ask for and what they actually want are often different things. This rule closes that gap before any code exists. Ask the minimum set of clarifying questions needed to avoid wrong work; do not start implementing until the must-have questions are answered (or the user explicitly approves proceeding with stated assumptions).
When to Use
Apply this when:
- The ask is missing at least one of: who the user is, why they want it, what success looks like, what the binding constraint is.
- The request is conventional rather than specific ("build me a dashboard", "make it faster") and you cannot unpack the convention without guessing.
- You are tempted to start with assumptions you have not surfaced.
- The user explicitly says: "interview me", "grill me", "before we start, are we sure?", "stress-test my thinking".
Do NOT use when:
- The ask is unambiguous and self-contained ("rename this variable", "fix this typo").
- The user explicitly asks for speed over verification.
- Pure information requests ("how does X work?", "what does this code do?").
- Mechanical operations (renames, formats, file moves).
- You already have >= 9/10 confidence.
Non-interactive constraint: This rule needs a live, responsive user. Do not invoke in CI pipelines, scheduled runs, or autonomous loops. If the ask is underspecified in a non-interactive context, flag it as a blocker instead of guessing.
Core Process
Step 1: Detect underspecification
Treat a request as underspecified if any of these are unclear:
- Objective - what should change vs stay the same.
- Done - acceptance criteria, examples, edge cases.
- Scope - which files, components, or users are in/out.
- Constraints - compatibility, performance, style, deps, time.
- Environment - language/runtime versions, OS, build/test runner.
- Safety - data migration, rollout/rollback, risk.
If multiple plausible interpretations exist, assume it is underspecified.
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 · 175 lines · 2,128 tokens per session scan A bd89e5b45f0e
ask-me is a cursor rule published in the GitHub repository Brainy-Builds/ts-inspect-cli (2 stars, last pushed 13d ago), licensed MIT. It adds 2,128 tokens to every session, about $0.0106 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.