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 agentmods add skills/kirodotdev/kirocrew/grillnpx skills add kirodotdev/KiroCrew --skill grillgit clone --depth 1 https://github.com/kirodotdev/KiroCrewWhat 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 | $0.00127 | $0.00516 |
| Opus 5 | $0.00063 | $0.00258 |
| Sonnet 5 | $0.00025 | $0.00103 |
| Haiku 4.5 | $0.00013 | $0.00052 |
Grade A, and why
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 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
HARD RULE: One Question Per Turn
Your response MUST contain exactly ONE question. No exceptions. No "also" or "a few things." One question → wait → next question. Self-check: if you count more than one ? outside of quotes, delete the extras.
Activation
Explicit triggers ("grill me", "interview me", "challenge this"): Start immediately with the banner then ONE question:
🔥 Grill Mode — one concern at a time. Say "enough" when ready to move on.
Ambiguous triggers ("poke holes", "what am I missing", "think this through", "help me decide", etc.): Ask first:
One at a time, or full critique dump? [OPTIONS: Grill me one at a time | Just give me the full critique]
Turn Structure
Every grill turn = exactly this:
- Context (1-2 sentences) — why this matters
- Question — one decision only, ending with
? - My recommendation — what I'd pick and why (one line)
Rules
- Facts vs Decisions: Look up facts silently (code, config, memory). Only ask about decisions the user must make.
- Memory: Check lessons/memory first. If already decided, confirm: "Previously you decided X. Still holds?"
- Save answers:
learn_add(rule="<decision>", category="knowledge", scope="workspace")after each. - Document decisions: After 3+ decisions, offer once to capture them in a doc.
- Exit: On "enough"/"just do it" → summarize decisions, proceed to action. Don't implement mid-grill.
- Simple plans: If the plan is clear and simple, say so — don't manufacture questions.
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 · 36 lines · 127 tokens per session scan A 156a943b069b
grill is a skill published in the GitHub repository kirodotdev/KiroCrew (3,532 stars, last pushed yesterday), licensed Apache-2.0. It adds 127 tokens to every session and 516 once invoked, about $0.0006 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-30.
Other skills, from other repositories
reskin
Author a NEW skin for the reskinnable-demo app. A skin is a self-contained domain plugin under src/skins/ / that implements the frozen Skin contract (src/shell/skin-contract.ts) to swap the app's entire experience — brand, theme, layout, pages, tools, data, and agent — as a live sales demo. Use when the user says "add…
copilotkit-setup
Use when adding CopilotKit to an existing project or bootstrapping a new CopilotKit project from scratch. Covers framework detection, package installation, runtime wiring (managed Intelligence or self-hosted SSE), provider setup, and first working chat integration.
copilotkit-integrations
Use when wiring an external agent framework (LangGraph, CrewAI, PydanticAI, Mastra, ADK, LlamaIndex, Agno, Strands, Microsoft Agent Framework, or others) into a CopilotKit application via the AG-UI protocol.
a2ui-renderer
Render A2UI (Agent-to-UI declarative surfaces) in CopilotKit v2. Enable the runtime via CopilotRuntime({ a2ui: {...} }), then enable the provider via . Auto-activates via /info — do NOT manually pass renderActivityMessages. createA2UIMessageRenderer ships from @copilotkit/react-core/v2; low-level primitives…
copilotkit-develop
Use when building AI-powered features with CopilotKit v2 -- adding chat interfaces, registering frontend tools, sharing application context with agents, handling agent interrupts, and working with the CopilotKit runtime.
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.