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 darellchua2/opencode-config-template --skill grill-me-skillgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWrote 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/darellchua2/opencode-config-template/grill-me-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/grill-me-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/grill-me-skill.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.00035 | $0.00546 |
| Opus 5 | $0.00017 | $0.00273 |
| Sonnet 5 | $0.00007 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
grill-me-skill 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 3d 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.
What it actually says
What I do
I orchestrate a plain grilling session — a relentless interview that sharpens a plan or design, with no doc artifacts produced. I delegate entirely to grilling-skill (the model-invoked interview engine).
Use grill-with-docs-skill instead if you also want the session to capture CONTEXT.md (glossary) and ADRs inline.
When to use me
Use this skill when:
- You want to stress-test a plan or design via interview, but don't need durable doc artifacts
- A quick alignment check before building is enough
Trigger phrases:
- "grill me"
- "interview me about this plan"
- "stress-test this idea"
Core Workflow
Step 1: Load the engine
Delegate all behavior to grilling-skill. Do not reimplement the interview loop.
Step 2: Run the grilling session
Apply grilling-skill's rules:
- One question at a time, each with a recommended answer
- Explore the codebase instead of asking when possible
- Walk the decision tree branch-by-branch until resolved or the user wants to build
Step 3: Conclude
Summarise the resolved decisions and any open questions. No files are written.
Rules
- Do not reimplement the engine. Delegate to
grilling-skill. - No doc capture. If the user wants CONTEXT.md/ADR capture, redirect to
grill-with-docs-skill.
Integration with Other Skills
| Skill | Integration |
|---|---|
grilling-skill |
The interview engine I orchestrate |
grill-with-docs-skill |
The variant that ALSO captures CONTEXT.md + ADRs |
domain-modeling-skill |
Not used by me (that's grill-with-docs-skill's job) |
Example Usage
"Grill me about how we should structure the notifications module"
The skill will delegate to grilling-skill, which interviews one question at a time with recommendations until the decision tree is resolved. No docs are written.
References
grilling-skill- Interview enginegrill-with-docs-skill- Variant with doc capture
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.
- 3d ago First seen · 70 lines · 35 tokens per session scan A 17d66c422d8d
grill-me-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 546 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-09-03.
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…
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…