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-complexity-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/skills/stchiotis/library-first-engineering/lfe-complexity-check)<a href="https://agentmods.dev/skills/stchiotis/library-first-engineering/lfe-complexity-check"><img src="https://agentmods.dev/badge/skills/stchiotis/library-first-engineering/lfe-complexity-check/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-complexity-check"><img src="https://agentmods.dev/badge/skills/stchiotis/library-first-engineering/lfe-complexity-check.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.00066 | $0.00986 |
| Opus 5.5 | $0.00026 | $0.00394 |
| Sonnet 5.5 | $0.00013 | $0.00197 |
| Haiku 4.5 | $0.00007 | $0.00099 |
Grade A, and why
lfe-complexity-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 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LFE Complexity Check — Prompt-Based Complexity Analysis
Position in Pipeline
- Phase: 3 (Inspector sub-skill)
- Persona: Inspector (read-only; no src/ writes)
- Trigger: Invoked by
/lfe-inspectorSub-Skill Dispatch whenlfe-complexity-check: truein.docs/quality/inspector-config.md - Output:
.plans/checks/complexity_findings.md— aggregated by Inspector intocritique.md
Mission
Reason over changed code to identify complexity indicators that reduce maintainability. The goal is not to enforce arbitrary metrics but to surface patterns that will make future AI sessions harder to navigate and extend correctly.
Hard Rules
- Dispatch Context Required (refuse direct invocation): This skill is dispatched by
/lfe-inspectorStep 6 — it is not a Brain-typeable skill (perLLM_AGENT_GUIDE.md§8.8 Skill Invocation Authority). If invoked without.plans/builder_done.mdfor the current slice, halt immediately and reply: "/lfe-complexity-checkis an Inspector sub-skill dispatched by/lfe-inspector. It cannot be run standalone. Run/lfe-inspector— the dispatcher will invoke this sub-skill if it is enabled in.docs/quality/inspector-config.md(or via an## Inspector Overridessection inactive_plan.md)." Direct invocation produces orphaned findings files and breaks the Inspector's aggregation logic. - Prompt-Only: Reason over the diff only — no linters or complexity calculators.
- Diff-Scoped: Analyse only files listed in
builder_done.md. - Severity: High (will actively confuse the next AI session) / Medium (increases risk) / Low (style concern).
- Context Matters: A 25-line function that is purely a switch statement is less concerning than a 15-line function with 4 levels of nesting and side effects.
Inputs
.plans/builder_done.md— list of changed files.plans/active_plan.md— scope boundary
Workflow
Step 1: Extract Diff Scope
From builder_done.md, identify and read modified files.
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 · 90 lines · 66 tokens per session scan A 68a2c930f89a
lfe-complexity-check is a skill published in the GitHub repository StChiotis/Library-First-Engineering (46 stars, last pushed 3mo ago), licensed MIT. It adds 66 tokens to every session and 986 once invoked, about $0.0003 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.