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-hygienegit 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-hygiene)<a href="https://agentmods.dev/skills/stchiotis/library-first-engineering/lfe-hygiene"><img src="https://agentmods.dev/badge/skills/stchiotis/library-first-engineering/lfe-hygiene/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/skills/stchiotis/library-first-engineering/lfe-hygiene"><img src="https://agentmods.dev/badge/skills/stchiotis/library-first-engineering/lfe-hygiene.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.00042 | $0.01871 |
| Opus 5.5 | $0.00017 | $0.00748 |
| Sonnet 5.5 | $0.00008 | $0.00374 |
| Haiku 4.5 | $0.00004 | $0.00187 |
Grade A, and why
lfe-hygiene 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LFE Hygiene Audit
Position in Pipeline
- Phase: 5 (Hygiene sub-pipeline, Step 1)
- Persona: Archivist
- Trigger: Scheduled every 5 sessions (tracked in
pipeline_status.md) or manually by human - Next Step:
/lfe-improve-architecture(Step 2)
Mission
Ensure the repository remains LFE-compliant. Detect drift between the Library and the physical filesystem, and verify the coordination layer is clean.
Workflow
1. Floor Map Audit
- Read
.docs/README.md. - Scan the filesystem.
- Identify "Illegal" Files: Files that exist but are not registered in the Floor Map.
- Identify "Ghost" Files: Files listed in the Floor Map that no longer exist.
2. Coordination Layer Audit
The cleanup tiers in lfe-archivist/SKILL.md Step 5a/5b are the source of truth for which files should be present at each lifecycle moment. This audit checks for drift from those rules.
- Mission complete (
Mission State == [MISSION COMPLETE]or[BLANK CANVAS]): no execution OR planning files should remain. If any of01_grill_summary.md,02_prd.md,03_slices.md,plan_critique.md,active_plan.md,builder_done.md,tdd_report.md,critique.md,inspection_report.md,diagnosis_report.md,rework_directive.mdstill exist, or if.plans/checks/contains any files → flag as "Stale Coordination Files". - Between slices (
Mission State == [IN-FLIGHT: <phase>]and Active Persona is Architect): planning files (01_grill_summary.md,02_prd.md,03_slices.md) MAY exist; execution files (plan_critique.md,active_plan.md,builder_done.md,tdd_report.md,critique.md,inspection_report.md,diagnosis_report.md,rework_directive.md,.plans/checks/) MUST be absent — flag any present as "Partial Cleanup Skipped". - Mid-mission:
active_plan.mdexists but Active Persona is NOT Architect, plan-critique, or Builder → flag as "Orphaned Plan". - Plan critique checkpoint:
plan_critique.mdshould exist only between Plan Approval and Builder start. Ifplan_critique.mdexists ANDbuilder_done.mdexists → the critique file should have been cleaned up by Partial Cleanup; flag as "Stale Plan Critique". - Hygiene cycle:
hygiene_report.mdis owned by the Hygiene sub-pipeline; flag only if it persists outside an active hygiene cycle. - Verify the
Coordination Filesrow inpipeline_status.mdmatches the mainline files in.plans/(the nine checkboxes are01 02 03 plan plan_critique build tdd critique inspect). Conditional artifacts (diagnosis_report.md,rework_directive.md,hygiene_report.md,.plans/checks/*.md) intentionally have no checkbox — their presence on disk is not row-drift.
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 · 100 lines · 42 tokens per session scan A dd7cf93cdf6b
lfe-hygiene is a skill published in the GitHub repository StChiotis/Library-First-Engineering (46 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 1,871 once invoked, about $0.0002 per session on Opus 5.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
discount-review
Inspect the discount policy fixture with a repeatable review checklist and helper script.
code-review
Reviews code for bugs, security issues, and best practices.
deep-review
Parallel competency-based code review. Launches independent Agent reviewers per competency (security, performance, architecture, database, concurrency, error-handling, frontend, testing), each with a focused checklist and isolated context. Synthesizes findings into unified report with FIX/DEFER/ACCEPT triage. Use…
architecture-quality
Keep web applications, APIs and services readable as they grow: choose feature or domain seams, assign state ownership, enforce dependency direction, keep adapters thin, and verify file shape. Use when starting or extending a web app, backend, frontend, API or multi-page product; when a change makes a module hard to…
attest
Verifying spec compliance: extracts ACs from specs, adversarially checks conformance, generates BDD scenarios and traceability matrices. Use when impl must be proven to match a PRD/SRS/AC.
guardian
Gatekeeping Git/PR by classifying change essence and recommending granularity, naming, and strategy; the ship recipe also executes PR delivery (create, CI watch, merge, cleanup) with Ask First on merge. Use when PR preparation, commit strategy, or gated PR delivery is needed.