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 naimkatiman/continuous-improvement --skill grill-megit clone --depth 1 https://github.com/naimkatiman/continuous-improvementWrote 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/naimkatiman/continuous-improvement/grill-me)<a href="https://agentmods.dev/skills/naimkatiman/continuous-improvement/grill-me"><img src="https://agentmods.dev/badge/skills/naimkatiman/continuous-improvement/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.1 | $0.00065 | $0.01265 |
| Opus 5 | $0.00032 | $0.00633 |
| Sonnet 5 | $0.00013 | $0.00253 |
| Haiku 4.5 | $0.00006 | $0.00127 |
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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/grill-me — Interrogate the plan before executing it
Ported verbatim in behavior from mattpocock/skills productivity/grill-me (MIT, © 2026 Matt Pocock). Cold-storage snapshot at third-party/mattpocock-skills/skills/productivity/grill-me/SKILL.md; SHA pin in third-party/MANIFEST.md.
What this skill does
Interview the user relentlessly about every aspect of the plan until shared understanding is reached. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide a recommended answer.
Ask questions one at a time.
If a question can be answered by exploring the codebase, explore the codebase instead.
When to fire it
- The user has just stated a goal at a high level ("add auth", "speed up the API") with no spec underneath.
- A
/proceed-with-the-recommendationwalk is about to start but the recommendation list itself is ambiguous about scope or success criteria. - An RFC, PRD, or plan doc is being drafted and the user wants pressure on the assumptions before writing it.
- The user types "grill me", "stress-test this plan", or "interview me about X".
gateguardis firing because the agent does not have enough grounding to proceed safely on a Write/Edit/Bash — alignment is missing, not just facts.
How it differs from gateguard
gateguard is a tool-boundary gate that blocks Edit / Write / Bash until the agent provides concrete investigation (importers, schemas, user instruction). It catches the case where the agent thinks it knows enough to mutate state. grill-me is the conversational layer one floor above: it surfaces the missing decisions before any tool call would even be attempted. They compose:
| Gap | Caught by |
|---|---|
| Agent has no spec, no plan — about to invent one | grill-me |
| Agent has a plan but specific branches are under-specified | grill-me |
| Agent is about to Edit / Write / Bash without grounding | gateguard |
| Plan exists, grounded, but the implementation drifts | verification-loop, tdd-workflow |
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 · 67 lines · 65 tokens per session scan A f3a1b793ccbe
grill-me is a skill published in the GitHub repository naimkatiman/continuous-improvement (7 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 1,265 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
opensrc
Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for"…
nopus-configure
Configure nopus complexity sensitivity, extra-simple rewrites, rewrite evidence, and Pi response hiding for this user.
nopus-simplify
Rewrite the immediately preceding assistant response with clearer and more direct prose when the user invokes this skill.
agentpush
Bridge an imported agentpush MCP server (Telegram, WhatsApp, etc.) with live agentproto sessions via the daemon's transmitter subsystem: transmitmessage sends outbound and binds the recipient to a session, inboundwatcherstart polls agentpush for new messages, and inboundendpointcreate/POST /inbound(/:slug) route…
bureau
Drive Bureau — the browser stack's installable capability server: a stealth Firefox (Camofox) + daemon that exposes browser tools as MCP-over-HTTP on :8830, plus a CLI for saved browser identities (sessions), social capture / search, adapter health probes, declarative workflows, and Guilde connection. Use when working…
agentproto-apps
Operate and build Agentproto apps — AIP-42 app bundles (defineApp().emit(dir), APP.md + agents/ + workflows/ + ui/) and their daemon lifecycle (appinstall, appapply, apprun, appstatus, appstop) plus the app-scoped durable data plane (appdataread/write/list/migrate). Covers serving one with a UI (agentproto app serve →…