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/amanidawn/dgame/grill-with-docsnpx skills add AmaniDawn/DGame --skill grill-with-docsgit clone --depth 1 https://github.com/AmaniDawn/DGameWrote 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/amanidawn/dgame/grill-with-docs)<a href="https://agentmods.dev/skills/amanidawn/dgame/grill-with-docs"><img src="https://agentmods.dev/badge/skills/amanidawn/dgame/grill-with-docs.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.00071 | $0.00716 |
| Opus 5 | $0.00036 | $0.00358 |
| Sonnet 5 | $0.00014 | $0.00143 |
| Haiku 4.5 | $0.00007 | $0.00072 |
Grade A, and why
grill-with-docs 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 6d 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.
This is a copy
100% identical to grill-with-docs — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Grill With Docs
对代码变更进行深度审查，利用项目文档提供架构上下文。
何时使用
当用户要求代码审查，或当你需要对变更进行比表面审查更深入的分析时。
流程
1. 收集上下文
在审查任何代码之前，收集相关的项目文档：
- ADR（架构决策记录）— 查找
.adr/或docs/adr/目录。这些记录了关键决策及其理由。审查应验证变更是否与现有决策一致，或是否需要新的 ADR。 - CONTEXT.md — 查找项目根目录或相关包中的
CONTEXT.md文件。这些描述了模块的领域概念和关系。审查应使用此词汇来评估变更是否正确地建模了领域。
参见 ADR-FORMAT.md 和 CONTEXT-FORMAT.md 了解这些文档的预期格式。
2. 审查变更
对于每个变更，评估：
- 领域忠实度 — 变更是否正确建模了领域？是否与 CONTEXT.md 中的概念一致？
- 架构一致性 — 变更是否与现有 ADR 一致？是否引入了需要新 ADR 的决策？
- 模块深度 — 变更是否改善了模块深度（简单接口，深层实现）？还是增加了浅层性？
- 接缝放置 — 变更是否在正确的位置引入了接缝？接缝是否被至少两个适配器（adapter）证明是合理的？
- 泄漏 — 变更是否将知识泄漏到了不该去的模块？是否违反了封装？
3. 产出审查结果
对每个发现：
- 引用支持该发现的 ADR 或 CONTEXT.md
- 如果变更与 ADR 矛盾，建议要么修改变更，要么创建新的 ADR
- 如果变更引入了领域概念但 CONTEXT.md 中没有，建议更新 CONTEXT.md
- 使用 LANGUAGE.md 中的词汇来描述架构问题
原则
- 文档是规范，代码是实现。 当代码与文档矛盾时，审查应标记这一点——并建议哪个应该改变。
- 审查应教学。 引用 ADR 和 CONTEXT.md 不仅是为了证明审查观点，也是为了教作者为什么做出这些决策。
- 没有文档不是借口。 如果项目没有 ADR 或 CONTEXT.md，审查仍应进行——但应建议创建它们，特别是对于架构性变更。
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 49 lines · 71 tokens per session scan A ffb17374fbeb
grill-with-docs is a skill published in the GitHub repository AmaniDawn/DGame (153 stars, last pushed 3d ago), licensed MIT. It adds 71 tokens to every session and 716 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to grill-with-docs, differing in 0 lines, and is treated as a copy.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…