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-dep-auditgit 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-dep-audit)<a href="https://agentmods.dev/skills/stchiotis/library-first-engineering/lfe-dep-audit"><img src="https://agentmods.dev/badge/skills/stchiotis/library-first-engineering/lfe-dep-audit.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.1 | $0.00081 | $0.01334 |
| Opus 5 | $0.00041 | $0.00667 |
| Sonnet 5 | $0.00016 | $0.00267 |
| Haiku 4.5 | $0.00008 | $0.00133 |
Grade A, and why
lfe-dep-audit 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 7d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LFE Dependency Audit — Manifest Review + Human-Run Instruction
Position in Pipeline
- Phase: 3 (Inspector sub-skill)
- Persona: Inspector (read-only; no src/ writes)
- Trigger: Invoked by
/lfe-inspectorSub-Skill Dispatch whenlfe-dep-audit: truein.docs/quality/inspector-config.md - Output:
.plans/checks/dep_findings.md— aggregated by Inspector intocritique.md
Mission
Review any dependency manifest files touched by the current diff for known-risky version patterns, major version jumps, and unmaintained packages. Since actual vulnerability databases require tool execution, this skill emits a structured instruction block asking the Brain to run the appropriate audit command and paste the output — keeping the skill fully tool-agnostic.
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-dep-auditis 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. - No Tool Execution: Reason over manifest contents only; emit the audit command for the Brain to run rather than running
npm audit/pip audit/cargo audithere. - Manifest-Scoped: Audit only the dependency files that appear in
builder_done.md; skip unchanged manifests. - Emit Instruction Block: Always emit a "Brain Action Required" block for each detected manifest type — even if no static concerns are found — because dynamic vulnerability data requires runtime tools.
- Severity: High (version pinned to
*orlatest; known-risky major) / Medium (very old major; no upper bound) / Low (minor version drift).
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.
- 7d ago First seen · 119 lines · 81 tokens per session scan A cfa62ee0ca00
lfe-dep-audit is a skill published in the GitHub repository StChiotis/Library-First-Engineering (43 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 1,334 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 skills, from other repositories
cpp-coding-standards
C++ coding standards based on the C++ Core Guidelines (isocpp.github.io). Use when writing, reviewing, or refactoring C++ code to enforce modern, safe, and idiomatic practices.
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.
refactor-advisor
A code review helper that finds common design and maintenance problems in a codebase and suggests ways to restructure the code.
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…
openclaw-github-dedupe
Investigate a cluster of GitHub issues and PRs, determine canonical candidates, post duplicate/related status, preserve contributor credit, and execute cleanup actions. Supports autonomous mode for provided-link-only closeout, merge/fix follow-through, changelog, and post-merge issue/PR cleanup.