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 aryaniyaps/lamina --skill lamina-evaluationgit clone --depth 1 https://github.com/aryaniyaps/laminaWrote 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/aryaniyaps/lamina/lamina-evaluation)<a href="https://agentmods.dev/skills/aryaniyaps/lamina/lamina-evaluation"><img src="https://agentmods.dev/badge/skills/aryaniyaps/lamina/lamina-evaluation/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/aryaniyaps/lamina/lamina-evaluation"><img src="https://agentmods.dev/badge/skills/aryaniyaps/lamina/lamina-evaluation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00067 | $0.00333 |
| Opus 5 | $0.00034 | $0.00167 |
| Sonnet 5 | $0.00013 | $0.00067 |
| Haiku 4.5 | $0.00007 | $0.00033 |
Grade A, and why
lamina-evaluation 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 9d 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
Lamina Evaluation
Reference-loading protocol
- Match the request's primary evaluation method to one row below.
- Open that linked reference before answering. Add another only when a second method materially changes the answer; do not preload the directory.
- Start the response with
Using lamina-evaluation: <topic path(s)>so the selected evaluation lens is auditable.
Topic index
| Evaluation signal | Read | Adds |
|---|---|---|
| Need actors to attempt workflows and edge probes on a built product | Actor Evaluation | Persona-based walkthrough method and reproducible blockers |
| Need specialists to inspect a contract or live product through explicit lenses | Expert Lens Review | parallel lens coverage tied to evidence and contract refs |
| Need success metrics, analytics interpretation, or experiment claims | Metrics Discipline | measurement boundaries and anti-fabrication rules |
Working rule
Use the smallest sufficient reference set. Actor evaluation requires a runnable product; use expert review before build or when a lens-specific inspection is requested. Pair either with metrics discipline only when real measurements or a measurement plan are in scope.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 30 lines · 67 tokens per session scan A d244f3ab193a
lamina-evaluation is a skill published in the GitHub repository aryaniyaps/lamina (114 stars, last pushed 4d ago), licensed Apache-2.0. It adds 67 tokens to every session and 333 once invoked, about $0.0003 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
recipe-eval-prompt
Compares original and optimized prompts through repeated blind paired execution in git worktrees. Use when evaluating prompt improvement effects or learning prompt engineering through concrete examples.
harness-validate
Use when user invokes /harness-validate or wants to check whether a harness.yaml file is valid according to the Harness Protocol v1 JSON Schema. Reports validation errors with field paths and helpful fix suggestions.
ui-test
Runs UI tests described in plain English by driving real Chrome via the Claude-in-Chrome extension. Covers end-to-end flows (clicks, forms, assertions), visual checks (screenshot + optional baseline diff), accessibility (axe-core), performance (Web Vitals + light Lighthouse-style metrics), and an interactive --debug…
audit-ui-e2e
Runs a beginner-mind end-to-end UI audit of any running app — local dev server, staging, production, or a specific URL. Drives Chrome through every interactive element on the target surface, collects structured findings (severity, category, where, symptom, impact, repro, triage), and hands the result off to…
capture-screens
Automatically navigates a web app using Playwright MCP and captures context-aware named screenshots at each product feature state. Names each file semantically based on context (e.g., checkout-payment-form-filled.png). Outputs a manifest.json mapping filenames to descriptions and a summary report. Use when documenting…
visual-crawl
Crawls the running app at randomized breakpoints, screenshots visual issues, checks design token consistency, and tests interactive elements. Each run covers different ground by design. Trigger on: "visual QA", "audit the app visually", "screenshot all the pages", "check for visual regressions", "crawl the site for…