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/setrathexx/codex-engineering-workflow-pack/grill-with-docsnpx skills add SetraTheXX/Codex-Engineering-Workflow-Pack --skill grill-with-docsgit clone --depth 1 https://github.com/SetraTheXX/Codex-Engineering-Workflow-PackWrote 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/setrathexx/codex-engineering-workflow-pack/grill-with-docs)<a href="https://agentmods.dev/skills/setrathexx/codex-engineering-workflow-pack/grill-with-docs"><img src="https://agentmods.dev/badge/skills/setrathexx/codex-engineering-workflow-pack/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 | $0.00062 | $0.01083 |
| Opus 5 | $0.00031 | $0.00541 |
| Sonnet 5 | $0.00012 | $0.00217 |
| Haiku 4.5 | $0.00006 | $0.00108 |
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 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grill With Docs
Clarify a plan before implementation by checking what the repo already says, what the code already does, and what product decisions remain unresolved.
Do not interview blindly. Read first, ask only when the answer cannot be found in docs or code.
Read First
Look for project context:
CONTEXT.mddocs/agents/domain.mddocs/adr/docs/agents/issue-tracker.mddocs/agents/test-commands.md- relevant README, docs, specs, and plans
- code paths related to the user's idea
Use fast file search when possible:
rg --files
If setup docs are missing, infer context from existing repo files and say what is missing.
When To Use
Use this skill when the user has:
- a fuzzy feature idea,
- a refactor plan that may touch multiple modules,
- a product behavior that needs sharper language,
- a domain concept that may be overloaded,
- a plan that should be checked against existing ADRs,
- uncertainty about whether to write PRD, issues, prototype, or tests next.
Do not use it for already-approved implementation work unless a product or domain decision is still open.
Workflow
1. Restate The Plan
Summarize the user request in project language.
Include:
- intended outcome,
- affected users or callers,
- likely modules or surfaces,
- known constraints,
- what is still unclear.
If the user's words conflict with existing domain terms, call that out.
2. Check Existing Docs
Read relevant docs before asking questions.
Look for:
- canonical domain terms,
- ADRs that constrain the plan,
- prior decisions that should not be relitigated,
- test commands that affect verification,
- issue tracker conventions if follow-up issues may be created.
If docs and code disagree, surface the disagreement as a decision point.
3. Check Code When Useful
If a question can be answered by reading code, read code.
Examples:
- Existing API shape.
- Current validation rules.
- How state changes are represented.
- What tests already exist.
- Whether a concept already has a name.
- Whether an ADR is still reflected in implementation.
What ships with it
3 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.
- 4d ago First seen · 182 lines · 62 tokens per session scan A 75ada0741069
grill-with-docs is a skill published in the GitHub repository SetraTheXX/Codex-Engineering-Workflow-Pack (1 stars, last pushed 4d ago), licensed MIT. It adds 62 tokens to every session and 1,083 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-31.
Other skills, from other repositories
hns-lsel-curator
Local Self-Evolution Loop (LSEL) curator — the CLUSTER + drain engine for the GOOS-local PROPOSE→APPLY seam closure (SPEC-LSEL-LOCAL-EVOLUTION-001). Companion-offset drain of .moai/lessons-inbox.jsonl with a drain-side severity filter that drops the 65% Bash-timeout/sandbox noise, eventkey clustering with a frequency…
hns-workflow-ci-loop
Unified CI watch + auto-fix loop skill. Polls gh pr checks after /moai sync PR creation, classifies required vs auxiliary failures, attempts safe automated patches (max 3 iterations), and escalates semantic failures to the user. Use for CI loop workflow — NOT for general loop iteration patterns (see…
moai-harness-learner
Harness learning subsystem coordinator. Produces Tier 4 auto-update proposal payloads consumed by the orchestrator (which surfaces them via AskUserQuestion) and orchestrates Apply/Rollback flows. Triggers when harness learning proposals are pending or learning lifecycle management is needed.
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
moai-workflow-thinking
Sequential Thinking MCP for structured step-by-step analysis via --deepthink flag. Separate from UltraThink which is Claude's native extended reasoning mode. Use for multi-step analysis or architecture decisions.
hns-oss-docs-readme-sync
README 4-file synchronization procedure for the oss-docs harness: Korean README.ko.md as primary source, en/ja/zh derivation, the shared language-switcher header contract, section-order parity checklist, and the manual verification recipe (no linter exists for READMEs). Loaded by the content-author and…