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-perf-checkgit 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-perf-check)<a href="https://agentmods.dev/commands/stchiotis/library-first-engineering/lfe-perf-check"><img src="https://agentmods.dev/badge/commands/stchiotis/library-first-engineering/lfe-perf-check.svg" alt="Measured on agentmods" 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 | $0.00072 | $0.00226 |
| Opus 5 | $0.00036 | $0.00113 |
| Sonnet 5 | $0.00014 | $0.00045 |
| Haiku 4.5 | $0.00007 | $0.00023 |
Grade A, and why
lfe-perf-check 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 4d 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
Generated pointer — not the protocol. This command exists so
/lfe-perf-checkdispatches natively in Claude Code. The canonical skill lives at.agents/skills/lfe-perf-check/SKILL.md(LFE-SOURCE).
Read .agents/skills/lfe-perf-check/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.
- 4d ago First seen · 9 lines · 72 tokens per session scan A 6732c474b515
lfe-perf-check is a command published in the GitHub repository StChiotis/Library-First-Engineering (43 stars, last pushed 1mo ago), licensed MIT. It adds 72 tokens to every session and 226 once invoked, about $0.0004 per session on Opus 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 commands, from other repositories
AGENTS
Commander.js-based CLI commands registered in src/main.ts.
generate-rfcs
Break the PRD into sequential implementation RFCs.
create-prd
Create a PRD through guided step-by-step questioning.
manage-changes
Analyze and integrate PRD changes mid-development.
adk-ts-starter-sync
Synchronize shared boilerplate content across all starter template READMEs in apps/starter-templates//README.md.
tldr-help
Quick reference card for tldr modes, slash commands, and triggers.