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 saemihemma/lead-producer-oss --skill workflow-requirements-grillgit clone --depth 1 https://github.com/saemihemma/lead-producer-ossWrote 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/saemihemma/lead-producer-oss/workflow-requirements-grill)<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/workflow-requirements-grill"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/workflow-requirements-grill/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/saemihemma/lead-producer-oss/workflow-requirements-grill"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/workflow-requirements-grill.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.00060 | $0.00656 |
| Opus 5 | $0.00030 | $0.00328 |
| Sonnet 5 | $0.00012 | $0.00131 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
workflow-requirements-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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements Grill Workflow
Purpose
Sharpen a vague request into a specified one before specialists touch it. This is collaborative elicitation, not critique: the goal is to surface the decisions the user has not made yet and get them made, so downstream work is not built on guesses.
Use When
- A request is fuzzy, broad, or has unstated assumptions
- Multiple readings of the ask would lead to different work
- Key terms are undefined or used loosely
- The user asks to "grill me," "interview me," or "help me think this through" before building
Do NOT Use When
- The request is already specified and the next step is execution or review
- The work is a critique of an existing recommendation (use the Devil's Advocate pass)
- The decision is hard-to-reverse and the need is failure foresight (use
workflow-premortem) - The unknown is about an inherited codebase, not the user's intent (use
workflow-project-discovery)
Working Method
- Restate the request in one sentence and name what is ambiguous in it.
- Map the open decisions as a short decision tree: the choices that, once made, would let work proceed without guessing.
- Grill one decision at a time. Ask a sharp question, force a definition where a term is loose, and surface the trade-off. Do not dump every question at once.
- Recommend an answer for each open decision with brief rationale, so the user can accept rather than start from blank.
- Capture the sharpened spec: the decisions made, definitions fixed, and explicit out-of-scope items.
- Hand back to Lead Producer with the spec so LP can route, and flag any decision the user deferred as an open question.
Default Output
REQUIREMENTS GRILL
==================
Request (restated): one sentence
Ambiguities: what was unclear
Decisions (resolved): each open question, the answer chosen, why
Definitions fixed: loose terms now pinned down
Out of Scope: what this explicitly is not
Still Open: decisions the user deferred (flagged for LP)
Sharpened Spec: the now-routable statement of work
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 · 49 lines · 60 tokens per session scan A 3385c45f4d69
workflow-requirements-grill is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed 8d ago), licensed MIT. It adds 60 tokens to every session and 656 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
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…