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-visual-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-visual-check)<a href="https://agentmods.dev/skills/stchiotis/library-first-engineering/lfe-visual-check"><img src="https://agentmods.dev/badge/skills/stchiotis/library-first-engineering/lfe-visual-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-visual-check"><img src="https://agentmods.dev/badge/skills/stchiotis/library-first-engineering/lfe-visual-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.00090 | $0.01510 |
| Opus 5.5 | $0.00036 | $0.00604 |
| Sonnet 5.5 | $0.00018 | $0.00302 |
| Haiku 4.5 | $0.00009 | $0.00151 |
Grade A, and why
lfe-visual-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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LFE Visual Check — Render, Reason, Hand the Verdict to the Human
Position in Pipeline
- Phase: 3 (Inspector sub-skill)
- Persona: Inspector (read-only; writes only
.plans/checks/) - Trigger: Invoked by
/lfe-inspectorSub-Skill Dispatch when armed — eitherlfe-visual-check: truein.docs/quality/inspector-config.md/## Inspector Overrides, or the Visual Floor auto-arms it because the slice's changed files touch a visual file class (the floor is a minimum; an override leaves it armed). - Output:
.plans/checks/visual_findings.md— aggregated by the Inspector intocritique.md, and the basis for the human visual sign-off at the finalization gate.
Mission
Give the Inspector eyes. Render the changed UI surface, reason over what it shows, and present it to the human for a visual verdict. The Inspector asserts the technical pass on its own authority; the visual verdict belongs to the human alone. This sub-skill renders and presents — the human alone declares whether it looks right.
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-visual-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 armed in.docs/quality/inspector-config.md(or via an## Inspector Overridessection inactive_plan.md), or auto-armed by the Visual Floor." Direct invocation produces orphaned findings files and breaks the Inspector's aggregation logic. - Artifact-free: Reason over the in-context render and write prose only. This skill saves no image files — keeping the blank-canvas seal intact and the run self-cleaning. (Render tools return the pixels in-context; capture the reasoning, leave the bytes unsaved.)
- Render-then-reason: Findings come from looking at the rendered surface, cited concretely (what element, what looks wrong).
- Defer the verdict: Write the findings and a human-action instruction; the human declares the visual verdict at the finalization gate. This skill records no
visual_confirmed/visual_signoffitself — that is the Inspector's finalization act, taken on the human's word. - Diff-scoped: Reason about the visual file classes changed in
builder_done.md; skip unrelated surfaces.
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 · 84 lines · 90 tokens per session scan A a442bac3d642
lfe-visual-check is a skill published in the GitHub repository StChiotis/Library-First-Engineering (46 stars, last pushed 3mo ago), licensed MIT. It adds 90 tokens to every session and 1,510 once invoked, about $0.0004 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
ui-design
Unify product UI design, frontend implementation, and verification. Use when asked to design, redesign, build, or fix a web, desktop, or mobile interface; a page, dashboard, form, component, design system, responsive layout, accessibility, interface animation, or editable hero/banner/infographic within a product…
frontend-design
A design guide for building polished web interfaces such as pages, dashboards, forms, navigation, and reusable UI components. It covers HTML, CSS, JavaScript, and common frontend frameworks.
muse
Defining and managing design tokens, applying token systems to existing codebases, building design system foundations. Use for spacing, color, typography, dark mode, cross-platform output.
native
Implementing production iOS/Android/macOS native features (SwiftUI, Compose) and iterating a screen against a reference design. Not for cross-platform RN/Flutter (Forge prototypes only; production is out of scope) or web (Artisan).
palette
Improving usability, interaction quality, cognitive load reduction, feedback design, and a11y compliance. Use when improving UX usability or interaction feel.
pixel
Generating pixel-accurate HTML/CSS code from image mockups (PNG/JPG/screenshots) and performing visual verification for faithful reproduction. Use when mockup-to-code generation is needed.