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 valtterimelkko/agent-workflow-skills --skill grill-megit clone --depth 1 https://github.com/valtterimelkko/agent-workflow-skillsWrote 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/valtterimelkko/agent-workflow-skills/grill-me)<a href="https://agentmods.dev/skills/valtterimelkko/agent-workflow-skills/grill-me"><img src="https://agentmods.dev/badge/skills/valtterimelkko/agent-workflow-skills/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/valtterimelkko/agent-workflow-skills/grill-me"><img src="https://agentmods.dev/badge/skills/valtterimelkko/agent-workflow-skills/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.00058 | $0.00359 |
| Opus 5 | $0.00029 | $0.00179 |
| Sonnet 5 | $0.00012 | $0.00072 |
| Haiku 4.5 | $0.00006 | $0.00036 |
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 11d 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
Interview me relentlessly about every important aspect of this plan until we reach a shared understanding.
Walk down each branch of the decision tree, resolving dependencies one by one. For each question, provide your recommended answer, but stay open to correction.
Ask questions one at a time.
If a question can be answered by exploring the codebase, existing docs, available memory, or context already present in the session, explore that first instead of asking me to repeat it.
When relevant, begin by identifying what kind of project this is and what context already exists. Distinguish between:
- what is already decided
- what is assumed but unverified
- what is still open
Do not depend on any specific file path or agent harness. Use whatever context is available in the current environment. If important context is missing, ask me to provide it.
As the discussion progresses, periodically checkpoint the emerging understanding in a lightweight way. Keep track of:
- key decisions made
- important constraints
- assumptions
- unresolved questions
- items that need external verification
Keep the process lean. Do not turn this into a giant framework or a long lecture. The goal is to uncover the missing context that will make downstream execution much stronger.
Stop when the important branches have been covered and there is a solid, practical shared understanding. Finish with a concise synthesis of:
- the project or plan
- the key decisions
- the main open questions or risks
- the most sensible next step
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.
- 11d ago First seen · 35 lines · 58 tokens per session scan A 17511776a906
grill-me is a skill published in the GitHub repository valtterimelkko/agent-workflow-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 58 tokens to every session and 359 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
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…