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 PerryLink/dsh-doublecheck --skill grill-requirementsgit clone --depth 1 https://github.com/PerryLink/dsh-doublecheckWrote 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/perrylink/dsh-doublecheck/grill-requirements)<a href="https://agentmods.dev/skills/perrylink/dsh-doublecheck/grill-requirements"><img src="https://agentmods.dev/badge/skills/perrylink/dsh-doublecheck/grill-requirements.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.00063 | $0.01056 |
| Opus 5 | $0.00032 | $0.00528 |
| Sonnet 5 | $0.00013 | $0.00211 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
grill-requirements 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
grill-requirements: the requirements furnace
You are an engineering discipline skill from dsh-doublecheck. Your job is to
turn a loose request into a checkable contract before any implementation
work starts. Double-check before you ship: grill the requirements, test the
implementation, prove the delivery. This skill owns the first verb — grill.
When to apply this skill
Use this skill when the current task is a software-engineering task (write code, change behavior, fix something, build a feature) and any of the following is true:
- The request is brief or open-ended and you cannot state its acceptance criteria from the text alone.
- The request leaves the scope, the boundary, or the definition of done implicit.
- You would have to guess what the user wants before you could write the first line of code.
- The user asked for a plan, a design, or "do it properly" without naming the success conditions.
If the request already names concrete artifacts, exact behavior, and how success is verified, skip straight to recording the spec and implementing — grilling something that is already cooked wastes the user's time.
The six dimensions
Every requirements grill must settle these six dimensions. Treat an unanswered dimension as an open question, not as a license to assume.
- Goal — what outcome the work must produce. One sentence that a non-author can verify.
- Boundary — what is in scope and what is out of scope. Which files, packages, interfaces, or behaviors may change; which must not.
- Acceptance criteria — the observable checks that prove the work is done. Prefer criteria a test or a command can verify; avoid "it should work well".
- Failure modes — what can go wrong, and what the correct behavior is in each case (bad input, missing dependency, partial failure, rollback).
- Priorities — what to trade when the goals conflict (speed vs. correctness, breadth vs. depth, simplicity vs. completeness). What is optional and can be dropped.
- Non-goals — what the user explicitly does NOT want, even though a reasonable engineer might build it anyway.
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 · 99 lines · 63 tokens per session scan A 82c7d641f2a4
grill-requirements is a skill published in the GitHub repository PerryLink/dsh-doublecheck (20 stars, last pushed today), licensed Apache-2.0. It adds 63 tokens to every session and 1,056 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-30.
Other skills, from other repositories
dsh-web-skin-developer
Build a new skin for the dsh-web skin collection (DSH Web GUI) and publish it into the Skin Center — the first-level settings section — scaffold with scripts/dsh-skin-new, author the v2 skin.json manifest plus skin.css token remap (pure asset directory, no package.json, no build step), validate with scripts/dsh-skin…
dsh-sdk-upgrade
Safely select and install a compatible official @deepseek-ai SDK release for dsh plugin projects (dsh-web, dsh-trading, and similar monorepos) from npm using an isolated worktree, explicit cohort review, CI-equivalent validation, and controlled rollout — including syncing the project's declared DSH host-version floor…
dsh-web-sdk-compatibility
Adapt and repair dsh-web after an approved official @deepseek-ai SDK/runtime cohort is selected or installed. Compare public API, type, service-injection, module-table, protocol, and behavior changes; map every change to repository consumers; implement the smallest fixes and durable compatibility contracts; handle…
dsh-web-pet-developer
Create a pet for the dsh-pet plugin and integrate it into the dsh web GUI — author a v2 pet.json manifest plus an 8-column x 9-row atlas per the Codex/hatch-pet contract (live2d pets, voice packs and status decorations included), drop it into the pet-center user directory or contribute it as a built-in asset under…
manage-taskboard
Manage work in the native DeepSeek Harness Taskboard with exact task ids and optimistic versions. Use when an Agent must inspect project work, claim an eligible todo, record progress or blockers, verify an implementation, submit it for human review, or release its own claim; also use when a human asks how to accept…
industry-research-method
A Chinese-language method for researching an industry by mapping its supply chain, tracking policies and news, and writing sourced reports. It separates the chain into upstream inputs, midstream production, and downstream distribution or use.