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-scoutgit 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-scout)<a href="https://agentmods.dev/skills/stchiotis/library-first-engineering/lfe-scout"><img src="https://agentmods.dev/badge/skills/stchiotis/library-first-engineering/lfe-scout/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-scout"><img src="https://agentmods.dev/badge/skills/stchiotis/library-first-engineering/lfe-scout.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.00030 | $0.00408 |
| Opus 5.5 | $0.00012 | $0.00163 |
| Sonnet 5.5 | $0.00006 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
lfe-scout 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.
What it actually says
LFE Scout Mode — The Flyweight Path
Position in Pipeline
- Phase: 0.5 (Complexity Gate → Minor Fix path)
- Persona: Scout
- Trigger: Human selects "Minor Fix" at Complexity Gate
- Output: Maintenance Report → Archivist handoff
Mission
Perform rapid, non-architectural maintenance tasks (typos, UI tweaks, simple bug fixes).
🛡️ The Protective Layer
Before taking ANY action, perform a Structural Integrity Check:
- Is this structural? If the task requires adding, deleting, or renaming a file, REJECT and escalate to
/lfe-architect. - Is this root-level? If the task modifies a configuration file at the root (e.g., a root agent-config file,
package.json), REJECT and escalate. - Is this domain-heavy? If the task changes core logic as defined in
CONTEXT.md, REJECT and escalate.
Protocol
- Analyze: Identify the specific lines to change.
- Execute: Implement the fix directly using
replace_file_content. - Report: Output a Maintenance Report including:
- Action: What was changed?
- Rationale: Why was it non-architectural?
- Integrity Check: Confirm no files were added/deleted.
- Log: Update the
CHANGELOG.md. - Update Pipeline: Increment session count in
pipeline_status.md.
Handoff
Signal transition to Archivist for doc sync. Ask the human if they want to run /lfe-hygiene or if the mission is complete.
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 · 35 lines · 30 tokens per session scan A c1f1ba95c5e4
lfe-scout is a skill published in the GitHub repository StChiotis/Library-First-Engineering (46 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 408 once invoked, about $0.0001 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
credit-note-fixer
Fix the tiny credit-note formatting bug and rerun the exact targeted test command.
code-review
Reviews code for bugs, security issues, and best practices.
bug-reproducer
Find likely software bugs in a codebase, rank concrete bug candidates, and prove or reject them with focused regression tests before proposing a fix. Also turn bug reports, stack traces, screenshots, failing behavior, support tickets, and regressions into minimal reproducible cases with red-to-green evidence. Use when…
ripple
Analyzing pre-change impact across vertical (dependency chains, files) and horizontal (pattern consistency, naming) dimensions. Use to estimate blast radius before a refactor. No code.
sweep
Detecting unnecessary files, unused code, and orphaned files, and proposing safe deletion. Not for removal execution (Builder), repo structure (Grove), or scope cutting (Void).
refactoring-safely
Change the structure of code that already exists without changing what it does: smells as triggers, the named transformations (extract/inline, move feature, organise data, simplify conditionals), and above all the workflow that makes it safe — characterization tests first, one transformation at a time, green between…