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 agentmods add instructions/nimajafari/lighthouse-skill/agents-mdgit clone --depth 1 https://github.com/nimajafari/lighthouse-skillWrote 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/instructions/nimajafari/lighthouse-skill/agents-md)<a href="https://agentmods.dev/instructions/nimajafari/lighthouse-skill/agents-md"><img src="https://agentmods.dev/badge/instructions/nimajafari/lighthouse-skill/agents-md.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 | $0.00462 | $0.00462 |
| Opus 5 | $0.00231 | $0.00231 |
| Sonnet 5 | $0.00092 | $0.00092 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
lighthouse-skill AGENTS.md 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 3d 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
AGENTS.md
Guidance for AI coding agents working in this repository.
Project overview
A single Agent Skill that teaches an agent to run Google Lighthouse — CLI, performance budgets, CI, and the programmatic API — to measure and verify web quality.
Structure
lighthouse-skill/
├── README.md
├── LICENSE
├── .claude-plugin/ # Claude Code plugin + marketplace manifests
└── skills/
└── lighthouse/
├── SKILL.md # main instructions (keep under 500 lines)
├── scripts/
│ └── run-lighthouse.sh
└── references/
├── CLI-FLAGS.md
├── CI.md
└── PROGRAMMATIC-API.md
Conventions
- SKILL.md stays under 500 lines; push deep/look-up material into
references/. - Descriptions include trigger phrases so the skill activates on the right prompts.
- Code examples use ❌ bad / ✅ good where it clarifies, and prefer copy-pasteable commands.
- Scripts follow:
#!/bin/bash+set -euo pipefail; human logs to stderr, machine-readable JSON to stdout; cleanup trap for temp files; document dependencies (jq, Node/npx).
Accuracy notes
- Lighthouse evolves. Audit IDs and metric weights shift between major versions (see the v13 Insight Audits note in SKILL.md). When editing, prefer linking to upstream docs over hardcoding numbers that drift.
- Keep the lab-vs-field distinction prominent — Lighthouse is a lab tool; INP and real-user data come from the field (CrUX /
web-vitals).
Testing changes
- Validate the YAML frontmatter in
SKILL.md. shellcheck skills/lighthouse/scripts/run-lighthouse.sh.- Smoke-test the script against a real URL:
skills/lighthouse/scripts/run-lighthouse.sh https://example.com 1. - Confirm all referenced files exist and links resolve.
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.
- 3d ago First seen · 45 lines · 462 tokens per session scan A 9ab1608dc4d1
lighthouse-skill AGENTS.md is an instructions file published in the GitHub repository nimajafari/lighthouse-skill (2 stars, last pushed 2mo ago), licensed MIT. It adds 462 tokens to every session, about $0.0023 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-31.
Other instructions, from other repositories
web-quality-skills AGENTS.md
Instructions for addyosmani/web-quality-skills, covering agents.md, project overview, live audit routing, directory structure and skill format.
web-quality-skills CLAUDE.md
Instructions for addyosmani/web-quality-skills, covering claude.md, project summary, quick reference, available skills and key thresholds.
agent-audit AGENTS.md
AGENTS.md instructions for fullstackdegen/agent-audit, covering agent audit instructions, core rules, applying fix packs, what this tool covers and completion standard.
agent-audit CLAUDE.md
Claude Code instructions for fullstackdegen/agent-audit, covering claude code instructions, mcp setup, how to use reports, suggested claude prompt and working in this repository.
elix-scroll-3d AGENTS.md
Instructions for ElixIsmael/elix-scroll-3d, covering elix-scroll-3d, how to use and the rules that save the most rework.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).