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-archivist)<a href="https://agentmods.dev/commands/stchiotis/library-first-engineering/lfe-archivist"><img src="https://agentmods.dev/badge/commands/stchiotis/library-first-engineering/lfe-archivist/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-archivist"><img src="https://agentmods.dev/badge/commands/stchiotis/library-first-engineering/lfe-archivist.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.00040 | $0.00197 |
| Opus 5.5 | $0.00016 | $0.00079 |
| Sonnet 5.5 | $0.00008 | $0.00039 |
| Haiku 4.5 | $0.00004 | $0.00020 |
Grade A, and why
lfe-archivist 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.
This is a copy
88% identical to lfe-architect — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Generated pointer — not the protocol. This command exists so
/lfe-archivistdispatches natively in Claude Code. The canonical skill lives at.agents/skills/lfe-archivist/SKILL.md(LFE-SOURCE).
Read .agents/skills/lfe-archivist/SKILL.md now and execute its protocol exactly as written — including its position-in-pipeline preconditions and its coordination-file contract. Honor the Skill Invocation Authority rules (LLM_AGENT_GUIDE §8.8): if this skill is agent-dispatched only and was typed out of sequence, refuse and route through the assembly line. Any change to skill behavior belongs in the canonical file, never in this pointer.
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 · 9 lines · 40 tokens per session scan A f82be4477fbf
lfe-archivist is a command published in the GitHub repository StChiotis/Library-First-Engineering (46 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 197 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to lfe-architect, differing in 8 lines, and is treated as a copy.
Other commands, from other repositories
t00-git
A Git assistant that explains version-control commands and guides work with commits, branches, merges, pull requests, and conflicts. Git records code changes so developers can review, restore, and share versions.
t00-publish
A release-preparation command that copies a project into a GitHub staging folder and checks which files are safe to publish.
release
Prepara e pubblica una nuova release del plugin mcp-legal-it. Bumpa la versione in tutti i manifest, aggiorna i changelog e la description con il conteggio tool corretto, crea il release branch, merge in main e tagga.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
ship
Comprehensive pre-deployment verification to ensure release readiness.
ship
Pre-ship pipeline — test, review, then prepare a clean commit.