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 skills/drvoss/everything-copilot-cli/grill-menpx skills add drvoss/everything-copilot-cli --skill grill-megit clone --depth 1 https://github.com/drvoss/everything-copilot-cliWrote 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/drvoss/everything-copilot-cli/grill-me)<a href="https://agentmods.dev/skills/drvoss/everything-copilot-cli/grill-me"><img src="https://agentmods.dev/badge/skills/drvoss/everything-copilot-cli/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.01202 |
| Opus 5 | $0.00028 | $0.00601 |
| Sonnet 5 | $0.00011 | $0.00240 |
| Haiku 4.5 | $0.00006 | $0.00120 |
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 yesterday.
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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grill Me
Grill Me is a focused pre-implementation interrogation loop. Instead of brainstorming broadly, it forces the plan through one concrete question at a time when branches are dependent, or through a numbered batch when the open questions are independent, until the unknowns, dependencies, and tradeoffs are visible.
Unlike interview-me, which is for gathering missing intent and can switch into an async
questionnaire, Grill Me is for pressure-testing a plan that already exists through decision-focused
dialogue.
When to Use
- A plan sounds reasonable, but key assumptions have not been made explicit yet
- The user wants to stress-test a design, approach, rollout, or scope boundary before building
- You need to expose hidden dependencies and unresolved branches in the decision tree
- The next useful step is sharper questioning, not more implementation detail
When NOT to Use
| Instead of grill-me | Use |
|---|---|
| You need multiple competing viewpoints on a decision | council |
| The plan must be checked against existing docs, glossary terms, or ADRs | grill-with-docs |
| The implementation already landed and now needs review against the original spec | implementation-review |
Workflow
1. Pick the exact artifact to grill
Choose one target:
- a proposal
- a plan
- a spec
- a rollout idea
Do not grill an entire vague conversation. First compress the target into the thing that needs pressure-testing.
2. Default to linear questioning; batch only independent branches
Choose the mode before each round:
- Linear mode (default): use when one answer changes what you should ask next. Ask one question at a time and fully resolve that branch before moving on.
- Batch mode: use only when several questions are mutually independent and the extra round-trip cost is high enough that asking them together will materially save time. Present the whole ready set in one numbered round, with one decision per question and a recommended answer attached to each.
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.
- yesterday First seen · 153 lines · 55 tokens per session scan A fdd018610284
grill-me is a skill published in the GitHub repository drvoss/everything-copilot-cli (45 stars, last pushed 9d ago), licensed MIT. It adds 55 tokens to every session and 1,202 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 skills, from other repositories
winui-design
Use when designing, reviewing, or fixing WinUI 3: sample and control discovery with winapp find-ui, layout planning, control choice, Fluent Design alignment, Light/Dark/High Contrast theming, typography, spacing, brushes, accessibility, and XAML data-binding design. Load before authoring new XAML, reviewing UI PRs…
winui-dev-workflow
Build and run workflow for WinUI 3 apps with WinApp CLI 0.6+ — project creation with winapp new, project-mode winapp run, BuildAndRun.ps1 analyzer integration, crash diagnosis, and prerequisites. Use when creating, building, running, or fixing build errors in a WinUI 3 project.
winui-packaging
MSIX packaging, code signing, and distribution for WinUI 3 apps — build for release, certificate generation (winapp cert generate), certificate trust, code signing (winapp sign), self-contained deployment, CI/CD with GitHub Actions, and Microsoft Store submission. Use when preparing for release, creating MSIX…
winui-session-report
Analyze the current or a recent agent session (GitHub Copilot CLI or Claude Code) and generate a diagnostic report. Use only when the user explicitly asks for session feedback, agent debugging, or a review of what happened during a build session. Do not inspect session data automatically.
microsoft-build
Your companion for Microsoft Build 2026. Helps you find sessions relevant to your project, discover what's new for your tech stack, scaffold projects from sessions, and plan your event schedule. Activate when users mention sessions, schedule, what's new, Build, Ignite, AI Tour, Microsoft event, conference, or…
git-tidy
Git repository triage across branches, worktrees, stashes, remote refs, tags, remotes, artifacts, ignored-but-tracked files, large blobs, and maintenance. Correlates exact work for work-bearing carriers, runs protected read-only inventory for legacy scopes, reports coverage gaps, and recommends outcomes without…