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.
git 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/commands/stchiotis/library-first-engineering/lfe-session)<a href="https://agentmods.dev/commands/stchiotis/library-first-engineering/lfe-session"><img src="https://agentmods.dev/badge/commands/stchiotis/library-first-engineering/lfe-session/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/stchiotis/library-first-engineering/lfe-session"><img src="https://agentmods.dev/badge/commands/stchiotis/library-first-engineering/lfe-session.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.04442 |
| Opus 5.5 | $0.00000 | $0.01777 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (46 stars, last pushed 3mo 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
AGENTS
Commander.js-based CLI commands registered in src/main.ts.
tldr-review
One-line TLDR PR review comments (verdict first, no filler).
t00-perf-check
A command that checks a Claude Code setup, including automatically loaded instructions, token use, skills, and hooks. It is described in Chinese and produces a configuration report with optimization suggestions.
t00-playwright-test
A command for testing a locally running web app in a real browser with Playwright, a browser automation and testing tool. It checks normal user flows and selected edge cases, then reports results with screenshots.
t00-hot
A command for finding currently popular topics from sources such as Weibo, Baidu, Douyin, Google Trends, and Japanese Twitter trends. It can also search within a requested category or region.
t00-status
A status-report command for a T00 task workspace, using files that record communication, tasks, and the previous session's next steps.