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-security-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-security-check)<a href="https://agentmods.dev/skills/stchiotis/library-first-engineering/lfe-security-check"><img src="https://agentmods.dev/badge/skills/stchiotis/library-first-engineering/lfe-security-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-security-check"><img src="https://agentmods.dev/badge/skills/stchiotis/library-first-engineering/lfe-security-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.00060 | $0.01151 |
| Opus 5.5 | $0.00024 | $0.00460 |
| Sonnet 5.5 | $0.00012 | $0.00230 |
| Haiku 4.5 | $0.00006 | $0.00115 |
Grade A, and why
lfe-security-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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LFE Security Check — OWASP Top-10 Prompt Analysis
Position in Pipeline
- Phase: 3 (Inspector sub-skill)
- Persona: Inspector (read-only; no src/ writes)
- Trigger: Invoked by
/lfe-inspectorSub-Skill Dispatch whenlfe-security-check: truein.docs/quality/inspector-config.md - Output:
.plans/checks/security_findings.md— aggregated by Inspector intocritique.md
Mission
Systematically examine the implementation diff for security vulnerabilities using the OWASP Top-10 as a structured checklist. No external scanners, no Semgrep, no platform-specific tooling — reasoning over code only.
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.mdAND.plans/tdd_report.mdfor the current slice, halt immediately and reply: "/lfe-security-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 Analysis: All findings come from LLM reasoning over the diff — reason only, with no code execution or external API calls.
- Cite Evidence: Every finding must quote the specific code line or pattern that triggers the concern.
- Severity Triage: Rate each finding as Critical / High / Medium / Low. Only Critical blocks Builder re-run; others are advisory.
- Scope to Diff: Analyse only the files changed in
builder_done.md; skip unchanged code.
Inputs
.plans/builder_done.md— list of changed files.plans/tdd_report.md— context on what was implemented.plans/active_plan.md— scope boundary.docs/engineering/engineering-standards.md(if present) — project security baseline
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 · 98 lines · 60 tokens per session scan A 1b678054d6f0
lfe-security-check is a skill published in the GitHub repository StChiotis/Library-First-Engineering (46 stars, last pushed 3mo ago), licensed MIT. It adds 60 tokens to every session and 1,151 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.