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 Dianel555/DSkills --skill grill-megit clone --depth 1 https://github.com/Dianel555/DSkillsWrote 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/dianel555/dskills/grill-me)<a href="https://agentmods.dev/skills/dianel555/dskills/grill-me"><img src="https://agentmods.dev/badge/skills/dianel555/dskills/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/dianel555/dskills/grill-me"><img src="https://agentmods.dev/badge/skills/dianel555/dskills/grill-me.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.01289 |
| Opus 5.5 | $0.00020 | $0.00516 |
| Sonnet 5.5 | $0.00010 | $0.00258 |
| Haiku 4.5 | $0.00005 | $0.00129 |
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 1mo 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grill Me
Turn an incomplete idea into an evidence-backed, actionable plan. Scale the depth to the work without adding unnecessary process.
Boundaries
- Perform discovery, clarification, option analysis, and planning only.
- Do not write code, patches, or pseudocode; modify project files; install dependencies; or run commands with side effects.
- Do not invoke or depend on OC, OpenSpec, or their workflows.
- Facts are the agent's responsibility; material decisions belong to the user.
- Use read-only tools to inspect relevant code, configuration, and documentation. Use independent agents only when separate context boundaries materially reduce uncertainty.
- Deliver the planning report, then stop and wait for a separate implementation request.
Adaptive Depth
Scale depth, not ceremony:
- Lightweight: For narrow, reversible, low-risk work, inspect only direct context, ask no questions when the input is sufficient, target zero to two rounds, and keep the report concise.
- Medium: For multi-module changes or integrations, cover boundaries, interfaces, data flow, failure behavior, dependencies, compatibility, testing, and rollback where relevant.
- Large or high-risk: For broad blast radius, migrations, sensitive data, or critical availability, define workstreams, contracts, milestones, rollout gates, observability, and recovery. Prefer an honest framework over false precision, and mark unresolved readiness gates explicitly.
Remain planning-only at every depth; do not silently switch workflows.
Process
1. Frame and Investigate
Extract the desired outcome, target users, current state, deliverable, scope, non-goals, constraints, and observable acceptance criteria.
Investigate facts that can change the plan. Cite repository paths, configuration, documentation, or external sources when they support a conclusion, and distinguish verified facts from assumptions.
Cover only relevant planning dimensions:
- User flows, expected behavior, edge cases, and failure states
- Architecture, conventions, integrations, interfaces, data ownership, and migration
- Security, privacy, reliability, performance, accessibility, and compatibility
- Dependencies, rollout, rollback, observability, support, and maintenance
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.
- 1mo ago First seen · 131 lines · 51 tokens per session scan A b42d5135e223
grill-me is a skill published in the GitHub repository Dianel555/DSkills (65 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 1,289 once invoked, about $0.0002 per session on Opus 5.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
meeting-notes
Estructura y formatea notas de reunión siguiendo las mejores prácticas de PM. Úsalo cuando te pidan crear notas de reunión, formatear notas de discusión, capturar elementos de acción, o documentar decisiones de cualquier tipo de reunión. Produce notas estructuradas con decisiones, elementos de acción (responsable +…
incident-postmortem
Escribe un postmortem de incidente estructurado o revisión post-incidente. Úsalo cuando se te pida escribir un postmortem, reporte de incidente, revisión P1/P2, reporte de apagón o RCA (análisis de causa raíz). Produce un postmortem sin culpables con cronología, causa raíz, factores contribuyentes, resumen de impacto…
stakeholder-update
Crear actualizaciones ejecutivas concisas para stakeholders usando el framework BLUF (Bottom Line Up Front). Usa cuando te pidan escribir una actualización de estado, reporte de progreso, comunicación de proyecto o briefing ejecutivo para liderazgo o stakeholders. Produce una actualización encabezada por BLUF con…
technical-debt-register
Documenta y prioriza un backlog de deuda técnica con impacto empresarial, estimaciones de esfuerzo y estrategia de resolución. Úsalo cuando se te pida auditar deuda técnica, crear un registro de deuda, priorizar deuda técnica para un trimestre, documentar atajos arquitectónicos o construir una hoja de ruta de…
cs-health-scorecard
Construir un cuadro de mando de salud del cliente para una cuenta específica. Úsalo cuando te pidan calificar la salud de la cuenta, evaluar el riesgo de renovación, construir un panel de salud o evaluar la probabilidad de que una cuenta se renueve o expanda. Produce un cuadro de mando de salud estructurado con estado…
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…