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.
git clone --depth 1 https://github.com/patrickserrano/lacquerWrote 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/plugins/patrickserrano/lacquer/rules)<a href="https://agentmods.dev/plugins/patrickserrano/lacquer/rules"><img src="https://agentmods.dev/badge/plugins/patrickserrano/lacquer/rules/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/plugins/patrickserrano/lacquer/rules"><img src="https://agentmods.dev/badge/plugins/patrickserrano/lacquer/rules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lacquer-rule-evals 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 22d 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
{
"name": "lacquer-rule-evals",
"version": "0.1.0",
"description": "Evaluate Lacquer's rendered per-profile Claude rules and synced skill routing.",
"author": { "name": "Patrick Serrano" }
}
What it installs
The manifest is a name and a version. 12 skills, 1 hook travel with it, and installing the plugin installs all of them — 821 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill ios-secrets-setup A 28 tokens
- Skill ios-ui-verification A 26 tokens
- Skill supabase-development-guide A 31 tokens
- Skill web-development-guide A 37 tokens
- Skill ios-build-verification A 29 tokens
- Skill ios-ci-configuration A 26 tokens
- Skill ios-project-development A 26 tokens
- Skill ios-release-guide A 28 tokens
- Skill marketing-council A 179 tokens
- Skill product-marketing A 110 tokens
- Skill copywriting A 174 tokens
- Skill marketing-ideas A 127 tokens
- Hook SessionStart A not measured
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.
- 22d ago First seen · 7 lines scan A 079bd4c5e957
lacquer-rule-evals is a plugin published in the GitHub repository patrickserrano/lacquer (4 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-24.
Other plugins, from other repositories
xcode-cli
Xcode CLI — Build, test, run, and manage Xcode projects from Claude Code.
epic
3 commands + 25 auto-trigger skills + self-evolving agent harness. Less to remember, more automation.
agented
A text editor for LLMs, not humans.
skillci
Lint, eval, and regression-test Claude Skills against a model matrix. Installs skillci-guardrails, which auto-verifies any SKILL.md an agent creates or edits with skillci check/eval before treating the change as done.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.