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 skills add s3rgiosan/agent-smith --skill grill-megit clone --depth 1 https://github.com/s3rgiosan/agent-smithWrote 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/s3rgiosan/agent-smith/grill-me)<a href="https://agentmods.dev/skills/s3rgiosan/agent-smith/grill-me"><img src="https://agentmods.dev/badge/skills/s3rgiosan/agent-smith/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/s3rgiosan/agent-smith/grill-me"><img src="https://agentmods.dev/badge/skills/s3rgiosan/agent-smith/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.00035 | $0.00581 |
| Opus 5 | $0.00017 | $0.00291 |
| Sonnet 5 | $0.00007 | $0.00116 |
| Haiku 4.5 | $0.00003 | $0.00058 |
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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grill Me
Purpose
Interview the user relentlessly about a plan, decision, or design until both sides reach a shared understanding — every branch of the decision walked, nothing silently assumed. For each question, provide your recommended answer with a short rationale.
The Design Tree
Map the plan as a design tree: every decision branches into the decisions that hang off it. Your job is to visit every branch, not to march through a flat list.
Working in Rounds
Work the tree in rounds, driven by the frontier — every decision whose prerequisites are already settled, i.e. the questions you can ask now without guessing at answers you haven't heard yet.
- Ask the whole frontier in one round. Number each question; give each a recommended answer.
- Wait for the user's answers before the next round.
- Each answer reshapes the tree — settled decisions push the frontier outward and unblock questions that depended on them. Recompute the frontier and ask the next round.
- A question whose answer depends on another question still open in this round belongs to a later round, not this one.
Format each question like so:
❓ **Q1** — **<question title>**: <question body; may be multiple paragraphs, may include options>
➡️ <your recommended answer + short rationale>
Facts Are Your Job, Never the User's
When a frontier question needs a fact from the environment (filesystem, codebase, tools), find it yourself — don't ask the user for anything you could look up.
- If a question can be answered objectively from the codebase with quick read-only checks, inspect first.
- When the lookup is non-trivial, dispatch a sub-agent to find it. Don't block the whole frontier on it: a running exploration is an unsettled prerequisite, so only the questions downstream of it wait — ask the rest of the frontier now.
- If evidence and the user's statement conflict, surface the conflict and ask for resolution.
The decisions are the user's — put each to them and wait. The facts are yours to gather.
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 · 55 lines · 35 tokens per session scan A 965fc54412c0
grill-me is a skill published in the GitHub repository s3rgiosan/agent-smith (3 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 581 once invoked, about $0.0002 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…
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…
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…