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 StChiotis/Library-First-Engineering --skill lfe-whats-nextgit 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-whats-next)<a href="https://agentmods.dev/skills/stchiotis/library-first-engineering/lfe-whats-next"><img src="https://agentmods.dev/badge/skills/stchiotis/library-first-engineering/lfe-whats-next.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.00036 | $0.00603 |
| Opus 5 | $0.00018 | $0.00302 |
| Sonnet 5 | $0.00007 | $0.00121 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
lfe-whats-next 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LFE What's Next
Purpose
Instant orientation. Read the pipeline state and tell the human exactly what step comes next.
Process
1. Read pipeline state
Read pipeline_status.md and extract:
- Active Persona
- Active Mission
- Pipeline Phase
- Coordination Files status
2. Scan coordination files
Check which files exist in .plans/:
01_grill_summary.md— grill complete?02_prd.md— PRD complete?03_slices.md— slices approved?active_plan.md— plan written for current slice?plan_critique.md— pre-build critique verdict? (PASS / WARN / BLOCK)builder_done.md— implementation complete?tdd_report.md— TDD pass complete?.plans/checks/*.md— Inspector sub-skill findings (if enabled)?critique.md— Inspector 4-Eyes pass complete?inspection_report.md— inspection verdict?diagnosis_report.md— bug diagnosis (only on first inspection failure)?
3. Determine next action
Based on what exists and what doesn't, output exactly one block:
📍 Phase <N>: <Phase Name> (Slice <X> of <Y>)
✅ Completed: <list of completed steps>
⬜ Next step: <exact skill to run>
🥸 Persona: <who should be active>
💬 Run: /lfe-<skill-name>
4. Edge cases
No coordination files exist + no active mission:
📍 No active mission.
💬 Start with: /lfe-boot
Session appears to have crashed mid-pipeline:
📍 ⚠️ Interrupted session detected.
Last completed: <last file found>
Resume from: /lfe-<next-skill>
🥸 Persona: <who should be active>
All slices complete, cleanup pending:
📍 All slices implemented and verified.
⬜ Next step: Archivist cleanup
💬 Run: /lfe-archivist
Hygiene due (session count ≥ 5 since last sweep):
📍 Mission complete.
⚠️ Architecture sweep due (5+ sessions since last).
💬 Run: /lfe-improve-architecture
Rules
- Never modify any files. This is a read-only skill.
- Output must be concise — max 5 lines.
- Use the coordination file presence as ground truth, not conversation context.
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 · 79 lines · 36 tokens per session scan A 0eca77fa1fcf
lfe-whats-next is a skill published in the GitHub repository StChiotis/Library-First-Engineering (43 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 603 once invoked, about $0.0002 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
lx
Codebase exploration tool that reads many files or whole directories in a single call, with per-file headers, glob include/exclude filters, function/type skeleton extraction (signatures only, no bodies), and head/tail line slicing.
flow-lean
Use when the user explicitly asks for Flow Lean, lean or less verbose output, action-first responses, expansion of a compressed Flow Lean answer, or Flow Lean recap and skills-footer controls.
prompt-optimization
Improves LLM-facing context while preserving intent, execution boundaries, and proportional work. Use when creating or reviewing prompts, agent definitions, skill definitions, or other instructions for an LLM.
recipe-eval-prompt
Compares original and optimized prompts through repeated blind paired execution in git worktrees. Use when evaluating prompt improvement effects or learning prompt engineering through concrete examples.
knowledge-base
Retrieves and updates project-specific prompt knowledge from comparison evidence and user feedback. Use only for prompt analysis or post-comparison learning within a Rashomon evaluation.
worktree-execution
Creates, pins, and cleans isolated Git worktree pairs for comparison trials. Use only when a Rashomon prompt or skill evaluation needs paired execution environments or orphan recovery.