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.
git 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-with-docs)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/grill-with-docs"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/grill-with-docs/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/rules/danielvm-git/bigpowers/grill-with-docs"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/grill-with-docs.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.00043 | $0.00589 |
| Opus 5.5 | $0.00017 | $0.00236 |
| Sonnet 5.5 | $0.00009 | $0.00118 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
grill-with-docs 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 1mo 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grill With Docs
Use this vs grill-me:
grill-with-docsis the doc-grounded variant ofgrill-me. Use it when the plan relies on external libraries or APIs and every challenge must be grounded in and cite a real documentation URL. Usegrill-mefor context-only assumption surfacing without fetching docs.
HARD GATE — Every challenge must cite a real documentation URL. No hallucinated APIs.
Process
- Read the plan or design under test (
specs/release-plan.yaml + epic shards, INTERFACE-OPTIONS.md, etc.). - List assumptions that depend on external libraries or APIs.
- For each assumption: fetch or quote official docs; challenge with "docs say X, plan says Y."
- Resolve or update the plan inline; unresolved items block
plan-work.
Docs mode rules
- Cite URL + quoted snippet (method name, parameter, version).
- If docs contradict the plan, plan loses until updated.
- Prefer official docs over blog posts.
Facts vs. Decisions Boundary
Distinguish between facts and decisions:
- Facts — things discoverable by reading docs, checking APIs, or exploring the codebase. 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 docs, go fetch it. Only ask questions where the user's judgment is needed.
Confirmation Gate
HARD GATE — Do NOT enact the plan or generate specifications until the user explicitly confirms shared understanding. Wait for explicit approval (e.g., "looks good", "confirmed", "proceed") before transitioning to any implementation, spec-writing, or task-slicing step.
Verify
→ verify: test -f skills/grill-with-docs/SKILL.md && test -f skills/grill-with-docs/REFERENCE.md
See REFERENCE.md for question templates.
Grill With Docs — Question templates
- "Docs at [URL] show signature
foo(bar?: Baz). Your plan callsfoo(bar, baz)— which is correct?" - "The changelog at [URL] deprecates X in v3. Your plan still uses X — migrate or pin version?"
- "Error handling in [URL] throws
NetworkError. Your plan catchesErroronly — is that sufficient?"
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.
- 1mo ago First seen · 53 lines · 43 tokens per session scan A 04ef59f7f78a
grill-with-docs is a cursor rule published in the GitHub repository danielvm-git/bigpowers (267 stars, last pushed 27d ago), licensed MIT. It adds 43 tokens to every session and 589 once invoked, about $0.0002 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-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.
general
API design standards — treat the API as a consumer-facing contract. Apply when designing, reviewing, or changing HTTP endpoints, routes, controllers, request/response payloads, and API resources.
00-project-rules
ContextOS core project rules and role orchestration.
vue
Rules for Vue (2 and 3) single-file components.
node
ContextOS rules for node.