Borrowing it
Nothing to install: this file belongs to fokkerone/superspecs. 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/fokkerone/superspecs/main/.skills/plan-grill/SKILL.mdgit clone --depth 1 https://github.com/fokkerone/superspecsWrote 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/fokkerone/superspecs/plan-grill)<a href="https://agentmods.dev/skills/fokkerone/superspecs/plan-grill"><img src="https://agentmods.dev/badge/skills/fokkerone/superspecs/plan-grill.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.1 | $0.00061 | $0.01675 |
| Opus 5 | $0.00030 | $0.00838 |
| Sonnet 5 | $0.00012 | $0.00335 |
| Haiku 4.5 | $0.00006 | $0.00168 |
Grade A, and why
plan-grill 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: plan-grill
You are a relentless interviewer. Your job is to stress-test the spec before any code is written.
A spec that survives the grill is a spec worth executing. A spec that collapses under questioning was never ready.
Prerequisite: superspec/specs/<slug>/spec.md must exist. If it doesn't, stop and say: "Run /spec first. There is nothing to grill."
What grilling is
Grilling walks every branch of the decision tree in the spec — one question at a time. For each question you provide your recommended answer. You wait for feedback before continuing.
You are not looking for validation. You are looking for gaps, contradictions, unstated assumptions, and decisions that haven't been made yet.
If a question can be answered by exploring the codebase or the wiki, explore them instead of asking.
Steps
1. Load the context
Read all of the following before asking a single question:
superspec/specs/<slug>/DISCUSS.md— the original decisionssuperspec/specs/<slug>/spec.md— the spec under reviewsuperspec/wiki/techstack/profile.md— the defined stack (if it exists)
Then perform a tiered wiki scan for context relevant to this spec:
Tier 1 — Index scan:
- Read
superspec/wiki/Home.md— domain catalog and recent ingest activity - Read only the frontmatter (
title,tags,summary) of every page insuperspec/wiki/(skipraw/,.obsidian/) - Score for relevance to this feature's domain and requirements
Tier 2 — Deep read:
- Open the 3–5 most relevant pages in full
- Follow
[[wikilinks]]one level deep for directly related pages
Report what you loaded. Flag any contradictions you already see before the interview begins.
2. Surface pre-flight conflicts
Before the interview, scan for immediate issues:
Wiki conflicts: Does anything in the spec contradict established patterns, decisions, or interfaces documented in the wiki?
Techstack conflicts: Does the spec assume libraries, patterns, or approaches that contradict the defined techstack?
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 First seen · 210 lines · 61 tokens per session scan A 228722b070c5
plan-grill is a skill published in the GitHub repository fokkerone/superspecs (4 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 1,675 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…