Borrowing it
Nothing to install: this file belongs to jepegit/issue-flow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jepegit/issue-flow/main/.cursor/skills/grill-me/SKILL.mdgit clone --depth 1 https://github.com/jepegit/issue-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/jepegit/issue-flow/grill-me)<a href="https://agentmods.dev/skills/jepegit/issue-flow/grill-me"><img src="https://agentmods.dev/badge/skills/jepegit/issue-flow/grill-me/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/skills/jepegit/issue-flow/grill-me"><img src="https://agentmods.dev/badge/skills/jepegit/issue-flow/grill-me.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.00073 | $0.00641 |
| Opus 5.5 | $0.00029 | $0.00256 |
| Sonnet 5.5 | $0.00015 | $0.00128 |
| Haiku 4.5 | $0.00007 | $0.00064 |
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 8d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grill me — relentless planning interview
Interview the user about every aspect of the plan until you reach a shared,
unambiguous understanding. Walk down each branch of the design tree, resolving
dependencies between decisions one at a time. The goal is to surface hidden
assumptions and edge cases before they get encoded in code or written into
.issueflows/01-current-issues/issue<N>_plan.md.
When to use
- The user asks to be grilled / stress-tested ("grill me", "poke holes in this").
- During
/iflow-plan, when grilling is active (see Activation below), to pressure-test the approach before the plan file is drafted.
How to grill
- One question at a time. Ask exactly one, then wait for the answer before moving to the next branch.
- Always recommend an answer. For each question, give your recommended option and a one-line rationale, so the user can accept quickly or push back.
- Explore before asking. If a question can be answered by reading the code,
the issue text, or
.issueflows/04-designs-and-guides/, explore first and confirm what you found instead of asking the user to do your homework. - Follow the decision tree. Resolve upstream decisions before the ones that depend on them; let earlier answers prune later branches.
- Stay on scope. Grill the issue at hand. Park genuinely separate concerns as follow-up notes rather than expanding the interview indefinitely.
- Know when to stop. End when every open branch is resolved (or explicitly deferred) and you can restate the plan without ambiguity. Summarize the agreed decisions so they can flow straight into the plan.
Activation
This skill is dormant by default: it engages only when the user asks for it ("grill me") or when a project turns it on for planning.
Turn it off again for the rest of a session with "stop grilling" or
"normal mode". (To make grilling on by default during planning for this
project, set grill_me_default = true under [issueflow] in
.issueflows/config.toml and re-run issue-flow update.)
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.
- 8d ago Changed 5767aa6aab7f
- 1mo ago Changed 179c27ef104a
- 2mo ago First seen · 58 lines · 73 tokens per session scan A eebf8df68f8a
grill-me is a skill published in the GitHub repository jepegit/issue-flow (4 stars, last pushed 8d ago), licensed MIT. It adds 73 tokens to every session and 641 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…