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/danielvm-git/bigpowers/grill-megit clone --depth 1 https://github.com/danielvm-git/bigpowersWrote 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/rules/danielvm-git/bigpowers/grill-me)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/grill-me"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/grill-me.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.00055 | $0.01074 |
| Opus 5 | $0.00028 | $0.00537 |
| Sonnet 5 | $0.00011 | $0.00215 |
| Haiku 4.5 | $0.00006 | $0.00107 |
Grade A, and why
grill-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 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grill Me
Use this vs grill-with-docs:
grill-mesurfaces assumptions from the conversation and context alone — no documentation fetching. Usegrill-with-docs(the doc-grounded variant) when the plan relies on a specific library or external API and every challenge must cite a real doc URL.
Two modes. Default is Design. Switch to Docs by saying "grill me with docs" or when the plan relies on a specific library or external API.
HARD GATE — Do NOT accept a design until every hard decision has been stress-tested. "Seems right" is not a decision. Grilling must identify and resolve tensions before build begins.
Design mode (default)
Interview relentlessly about every aspect of this plan until reaching shared understanding. Walk each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer. Ask one question at a time.
If a question can be answered by exploring the codebase, explore it instead.
Facts vs. Decisions Boundary
Distinguish between facts and decisions:
- Facts — things discoverable by exploring the codebase, reading docs, or checking APIs. Do not ask the user to confirm facts; find them yourself.
- Decisions — choices that require user input (trade-offs, preferences, priorities). Always present options and ask the user to choose.
Never "grill yourself" — if the answer is in the code, go find it. Only ask questions where the user's judgment is needed.
Docs mode
Ground every challenge in real documentation — no assumption about a library's behavior goes unchecked. See REFERENCE.md for the full process.
Short form:
- List every external library, third-party API, and framework behavior relied upon.
- Fetch the actual docs for each (
WebFetchthe official API reference). - Challenge each plan assumption against the real docs: correct method signature? right version? deprecated?
- Report confirmed ✓, corrected ✗ (with the real behavior), and uncertain →
spike-prototype. - Update the plan for each confirmed discrepancy.
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 First seen · 108 lines · 55 tokens per session scan A a0b65ef55f83
grill-me is a cursor rule published in the GitHub repository danielvm-git/bigpowers (163 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 1,074 once invoked, about $0.0003 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-09-03.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
app-router-patterns
Next.js 14+ App Router patterns — Server Components, Client Components, Route Handlers, Server Actions, and metadata API.
00-project-rules
ContextOS core project rules and role orchestration.
context-os
ContextOS rules for context-os.
database
Database architecture, schema design, Prisma, Drizzle ORM, indexing strategies, migrations, and N+1 query resolution.
vue
Rules for Vue (2 and 3) single-file components.