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-bootnpx skills add StChiotis/Library-First-Engineering --skill lfe-bootgit clone --depth 1 https://github.com/StChiotis/Library-First-EngineeringWhat 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.00036 | $0.01090 |
| Opus 5 | $0.00018 | $0.00545 |
| Sonnet 5 | $0.00007 | $0.00218 |
| Haiku 4.5 | $0.00004 | $0.00109 |
Grade A, and why
lfe-boot 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 3d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LFE Session Bootstrap
Protocol
Step 1 — Read the Entrance Card
Read pipeline_status.md. Extract and hold:
- Integrity Score (Verify it is green)
- Active Persona (Architect / Builder / Inspector / Archivist)
- Active Mission (The current goal)
- Pipeline Phase (Which phase and slice we're on)
- Coordination Files (Which steps are complete)
- Session Count (For hygiene scheduling)
Step 2 — Check for Interrupted Session or State Anomaly
Scan .plans/ for coordination files (01_grill_summary.md, 02_prd.md, 03_slices.md, active_plan.md, plan_critique.md, builder_done.md, tdd_report.md, .plans/checks/*, critique.md, inspection_report.md, diagnosis_report.md, hygiene_report.md). Resume mapping per LOOP_ARCHITECTURE.md §4 — the last present file determines the next skill.
-
Scenario A: Normal Interrupted Session If files exist in
.plans/and the entrance card state indicates the mission is in progress:"⚠️ Interrupted session detected. Last completed step: <step>. Resume from: /lfe-<next-skill>. Confirm?"
-
Scenario B: State Anomaly & Zoom-Out Comparison If files exist in
.plans/but the entrance card indicates the mission is complete or ready:- Leave the files in place; clear them only on explicit instruction.
- Invoke the
/lfe-zoom-outskill instructions to perform a high-level comparison: Compare the changes defined in the.plans/files against the current codebase insrc/**. - Inform the user of your findings immediately:
- If the plans match the code:
"⚠️ State Anomaly detected: Files exist in
.plans/but work was already completed and saved tosrc/**. The Archivist missed its cleanup step. Please clear the.plans/directory manually." - If the plans diverge from the code:
"⚠️ State Anomaly detected: Files exist in
.plans/but the changes were not saved to the codebase. This is a real interrupted session."
- If the plans match the code:
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.
- 3d ago First seen · 78 lines · 36 tokens per session scan A e98e6f9a10ac
lfe-boot 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 1,090 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
context-engineering
Manages agent context for effective AI-assisted development. Use when working on large codebases, when the agent seems to lack necessary context, when structuring CLAUDE.md or project guidance files, or when coordinating long multi-step development sessions.
GuoFanDirector_Skills
郭帆导演风格视听语言体系，涵盖分镜设计、场景气氛、预演动态等导演工作流知识.
general-video
Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated…
motion-graphics
A short, design-led motion graphic where motion is the message — kinetic typography, stat count-up, chart/data-viz hit, logo sting / brand lockup, lower-third / callout / social overlay, animated map (highlight regions, connect places, zoom to a location), animated tweet / news-article / headline, webpage / UI…
metrics-instrumentation
Specification for instrumenting an opik-backend workflow with operational OpenTelemetry metrics — per-stage throughput/latency/error counters and native histograms, dimensioned per-customer (workspace). Use when a pipeline (scoring, ingestion, experiments, jobs) needs per-stage visibility. Covers metric emission only…
embedding-strategies
Select and optimize embedding models for semantic search and RAG applications. Use when choosing embedding models, implementing chunking strategies, or optimizing embedding quality for specific domains.