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 ccoalm/ccl-skills --skill grill-megit clone --depth 1 https://github.com/ccoalm/ccl-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/ccoalm/ccl-skills/grill-me)<a href="https://agentmods.dev/skills/ccoalm/ccl-skills/grill-me"><img src="https://agentmods.dev/badge/skills/ccoalm/ccl-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/ccoalm/ccl-skills/grill-me"><img src="https://agentmods.dev/badge/skills/ccoalm/ccl-skills/grill-me.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 49 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00157 | $0.00860 |
| Opus 5 | $0.00078 | $0.00430 |
| Sonnet 5 | $0.00031 | $0.00172 |
| Haiku 4.5 | $0.00016 | $0.00086 |
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 4d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
grill-me — 轻量方案拷问
Use this when the user explicitly asks to grill, interview, challenge, or stress-test a plan before implementation.
This is a narrow pre-implementation interview. It clarifies the next blocking decision; it does not write the plan, own delivery gates, or replace the relevant owner workflow.
When to use
Use for explicit requests such as:
grill-me/grill me;- 访谈、拷问、追问一个方案；
- 压力测试方案、设计、API shape、数据模型、权限模型、工作流；
- before implementation, when several product or technical decisions depend on each other.
Do not auto-trigger this from generic “帮我规划 / scope 一下 / 写个方案”. Those route to the owning workflow first, usually product-rd-workflow.
Owner boundaries
- Full requirement shaping, spec, plan, lifecycle gates, or multi-step delivery →
product-rd-workflow. - Risk tags, gate selection, rollout or review requirements →
feature-risk-router. - Code-level YAGNI, delete-code, overengineering, or adversarial review of already-written code →
product-rd-workflow's independent-review gate (no dedicated CCL delete-code/YAGNI skill; the review gate owns it). - Test layers, fixtures, coverage, regression, CI gate design →
testing-strategy. - Bug/root-cause diagnosis →
defect-diagnosis. - Implementation → the relevant stack/dev skill or bounded executor.
- Reusable process/skill lesson extraction →
skill-extraction-workflow.
grill-me may feed those owners by resolving one unclear decision first. It must hand back once the user asks for a deliverable artifact, implementation, formal review, or test plan.
Core contract
Ask one blocking question at a time.
Each turn must include:
Target: the plan/design being challenged.Current assumption: the most important assumption currently visible.Question N: exactly one unresolved decision.Recommended answer: a concrete default.Why: short rationale and the risk if the answer is wrong.
Then wait for the user's answer before asking the next dependent question.
What ships with it
1 file 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.
- 4d ago Changed · +40 tokens per session d12c73e56c5d
- 10d ago First seen · 81 lines · 117 tokens per session scan A 261268b32df1
grill-me is a skill published in the GitHub repository ccoalm/ccl-skills (6 stars, last pushed today), licensed Apache-2.0. It adds 157 tokens to every session and 860 once invoked, about $0.0008 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
security-review
Perform a focused security review of pending git changes to identify high-confidence security vulnerabilities with real exploitation potential. Use this skill when the user asks for a security review, security audit, vulnerability scan, or wants to check pending changes on a branch for security issues before merging.…
huggingface-llm-trainer
Train or fine-tune language models with TRL or Unsloth on Hugging Face Jobs, including SFT, DPO, GRPO, reward models, and GGUF conversion. Use for cloud LLM training; use huggingface-vision-trainer for vision tasks.
feature-dev
Guide a feature implementation through a structured seven-phase workflow with deep codebase understanding, clarifying questions, parallel architecture design, and quality review. Use this skill when the user asks to build a new feature, add functionality, or wants a methodical approach to implementation rather than…
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
memstack-deployment-domain-ssl
Use this skill when the user says 'setup domain', 'configure DNS', 'SSL certificate', 'domain-ssl', 'custom domain', 'HTTPS setup', or needs to configure DNS records, SSL certificates, and custom domains for any hosting provider. Do NOT use for full deployment workflows.
memstack-development-refactor-planner
Use this skill when the user says 'refactor', 'refactoring plan', 'code cleanup', 'reduce duplication', 'simplify code', 'tech debt', 'god class', 'tight coupling', or needs to systematically improve existing code. Identifies targets, assesses risk, and builds incremental execution plans. Do NOT use for writing new…