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 commands/stchiotis/library-first-engineering/lfe-sessiongit 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.00000 | $0.04442 |
| Opus 5 | $0.00000 | $0.02221 |
| Sonnet 5 | $0.00000 | $0.00888 |
| Haiku 4.5 | $0.00000 | $0.00444 |
Grade A, and why
lfe-session 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 2d 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LFE Framework Improvement Session
You are acting as a senior framework architect helping improve the Library-First Engineering (LFE) framework. This is a META session — you are working ON the framework, not WITH it. Do NOT run the LFE pipeline (/lfe-boot, /lfe-architect, etc.) — those are for product repos that use LFE as a template.
Source of truth for framework state: GitHub Issues + git history. NOT the .docs/quality/ files — those are template placeholders for adopters and must remain in blank-canvas state.
Orientation Protocol
Execute these steps in order. Be concise — present findings, not narration.
Step 1 — Framework Identity Snapshot
Establish what the framework currently is (as opposed to what it's tracking):
- Read
README.md— extract claimed counts (skills, personas, pillars). These are public-facing assertions and must match reality. - Read
LLM_AGENT_GUIDE.md§9 — the canonical skill table. - Count
.agents/skills/*/SKILL.mdfiles — should match the claimed count. - Note current branch + active feature branches:
!git branch --show-current && git branch -a 2>/dev/null | head -20
Step 2 — Open Work Surface (GitHub Issues + PRs)
Framework work is tracked exclusively on GitHub. Read both issues and open PRs:
!gh issue list --limit 25 --json number,title,labels,updatedAt --jq '.[] | "#\(.number) [\(.labels | map(.name) | join(", "))] \(.title)"' 2>/dev/null || echo "GH unavailable"
!gh pr list --limit 10 --json number,title,isDraft,labels --jq '.[] | "PR #\(.number)\(if .isDraft then " (draft)" else "" end) [\(.labels | map(.name) | join(", "))] \(.title)"' 2>/dev/null || echo "No PRs"
Step 3 — Recent Activity
!git log --oneline -15 2>/dev/null || echo "No git history"
Step 4 — Structural Integrity Test Suite
Run these 12 tests. For each, output PASS / FAIL: . Failures become candidate focus areas in the briefing.
T1. Pipeline status canvas. pipeline_status.md exists. Mission State is [BLANK CANVAS]. All 9 coordination checkboxes present (01 02 03 plan plan_critique build tdd critique inspect). Session count is 0. Last sweep is none yet.
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.
- 2d ago First seen · 235 lines · 0 tokens per session scan A f7919766eae0
lfe-session is a command published in the GitHub repository StChiotis/Library-First-Engineering (43 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,442 tokens. 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 commands, from other repositories
vibe-agents
Step 4 of the vibe-coding workflow: generate AGENTS.md + tool configs so the AI builder stays on track.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
run
Command "run" from ErisPulse/ErisPulse, covering erispulse.cli.commands.run 模块, 模块概述, 类列表, class reloadhandler(filesystemeventhandler) and class runcommand(command).
init
Command "init" from ErisPulse/ErisPulse, covering erispulse.cli.commands.init 模块, 模块概述, 函数列表, validateprojectname(name: str) and 类列表.
install
Command "install" from ErisPulse/ErisPulse, covering erispulse.cli.commands.install 模块, 模块概述, 类列表 and class installcommand(command).
language
Command "language" from ErisPulse/ErisPulse, covering erispulse.cli.commands.language 模块, 模块概述, 类列表 and class languagecommand(command).