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/stchiotis/library-first-engineering/lfe-grill-with-docsnpx skills add StChiotis/Library-First-Engineering --skill lfe-grill-with-docsgit clone --depth 1 https://github.com/StChiotis/Library-First-EngineeringWrote 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/stchiotis/library-first-engineering/lfe-grill-with-docs)<a href="https://agentmods.dev/skills/stchiotis/library-first-engineering/lfe-grill-with-docs"><img src="https://agentmods.dev/badge/skills/stchiotis/library-first-engineering/lfe-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.00050 | $0.00839 |
| Opus 5 | $0.00025 | $0.00419 |
| Sonnet 5 | $0.00010 | $0.00168 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
lfe-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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LFE Grill With Docs
Position in Pipeline
- Phase: 1 (Architect sub-pipeline, Step 1)
- Persona: Architect
- Input: Human intent (conversation)
- Output:
.plans/01_grill_summary.md
Process
Interview the human relentlessly about every aspect of the plan until shared understanding is reached. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
Ask questions one at a time, waiting for feedback before continuing.
If a question can be answered by exploring the codebase or .docs/, explore instead of asking.
During the Session
Challenge against the glossary
When the human uses a term that conflicts with existing language in CONTEXT.md, call it out immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y — which is it?"
Sharpen fuzzy language
When the human uses vague or overloaded terms, propose a precise canonical term. "You're saying 'account' — do you mean the Customer or the User? Those are different things."
Discuss concrete scenarios
When domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force precision about boundaries between concepts.
Cross-reference with code
When the human states how something works, check whether the code agrees. If contradiction found, surface it: "Your code cancels entire Orders, but you just said partial cancellation is possible — which is right?"
Cross-context check (if applicable)
Before declaring any term, check whether .docs/domain/CONTEXT-MAP.md exists. If it does, verify whether the term is already declared in another context. If yes, prompt the Brain for the relationship classification (shared kernel / customer-supplier / translation / separate ways) and record the decision in CONTEXT-MAP.md.
Update CONTEXT.md and Domain Rules Inline
When a new domain term or math/business rule is resolved, you MUST update the project's development documents IMMEDIATELY:
- Canonical Terms: Append directly to
CONTEXT.md(root) and.docs/domain/glossary.mdright there. Capture each as it happens rather than batching. Use the format in CONTEXT-FORMAT.md. - Logic, Rules, & Calculations: Update
.docs/domain/domain-knowledge.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 · 86 lines · 50 tokens per session scan A fb5d806099e9
lfe-grill-with-docs is a skill published in the GitHub repository StChiotis/Library-First-Engineering (43 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 839 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
playwright
Use when the task requires capturing or automating a real browser from the terminal.
ai-engineering-toolkit
6 production-ready AI engineering workflows: prompt evaluation (8-dimension scoring), context budget planning, RAG pipeline design, agent security audit (65-point checklist), eval harness building, and product sense coaching.
promptfoo-provider-setup
Configure promptfoo providers or redteam targets for hosted models, live HTTP APIs, Python/JavaScript local scripts, agent SDKs, or multi-input systems. Use when connecting promptfoo to the system under test, mapping vars, auth env vars, request bodies, response transforms, or static-code-derived provider wrappers. Do…
prior-auth-packet-builder
Build a concise prior authorization packet from local case files and payer policy docs.
avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms"). Use this skill when asked to "remove AI-isms," "clean up AI writing," "edit writing for AI patterns," "audit writing for AI tells," or "make this sound less like AI." Supports a detect-only mode, an edit-in-place mode for files, an optional voice…
unlazy
Enforces completion discipline for substantial autonomous work by writing acceptance gates before execution, decomposing work with the Depth Tree, running approved checks, and re-verifying evidence before reporting. Use when an agent faces a long or multi-part task, work that has returned half-done, an exhaustive…