Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/patrickserrano/lacquernpx agentmods add skills/patrickserrano/lacquer/working-with-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/skills/patrickserrano/lacquer/working-with-lacquer)<a href="https://agentmods.dev/skills/patrickserrano/lacquer/working-with-lacquer"><img src="https://agentmods.dev/badge/skills/patrickserrano/lacquer/working-with-lacquer.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.00109 | $0.02426 |
| Opus 5 | $0.00055 | $0.01213 |
| Sonnet 5 | $0.00022 | $0.00485 |
| Haiku 4.5 | $0.00011 | $0.00243 |
Grade A, and why
working-with-lacquer 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 2d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working With Lacquer
Lacquer renders shared content — CLAUDE.md regions, skills, commands, lint
configs, git hooks, CI workflows — from one repo into every project. A project
declares its shape in .lacquer.toml; lacquer sync writes the content;
lacquer audit checks the project against it and is wired into CI.
The rule that explains every mechanism below: a lacquer-managed file is identical to the lacquer's copy, or it is excluded. There is no third state. A quietly-edited copy is how one project's pre-commit hook ends up weaker than its CI while looking healthy.
Is this file mine?
lacquer audit # classifies every managed unit, lists the ones that aren't clean
lacquer status # each CLAUDE region's stamped version vs the lacquer's latest
If audit lists it, the lacquer owns it. Typically: .swiftlint.yml,
.swiftformat, biome.json, deno.jsonc, .pre-commit-config.yaml,
lefthook.yml, .github/workflows/<profile>-*.yml, .claude/skills/**,
.claude/commands/**, and the <!-- lacquer:… --> regions inside CLAUDE.md
/ AGENTS.md. Text outside those markers in a CLAUDE.md is the project's and
is preserved.
Exit codes
| Code | Means | Fix |
|---|---|---|
| 0 | clean | — |
| 1 | the command failed (bad manifest, I/O, missing profile) | read the message |
| 2 | usage error | — |
| 3 | a managed file was edited locally; sync would clobber it | see below |
| 4 | a project baseline is not met | meet it, or time-box a relaxation |
| 5 | lacquer doctor: a check proved it cannot fail |
fix the check |
| 6 | a stack on disk is not declared in .lacquer.toml |
lacquer adopt |
Recipes
Exit 3 — "a lacquer-managed file was edited in this project." Decide which is true, then do that one:
- The change should apply everywhere → make it in the lacquer repo, open a PR there, then re-sync this project. This is the default and usually the right answer.
- This project genuinely owns the file → add it to
[project].excludewith areason(and anuntilif it is temporary — see "Exclusions" below). The lacquer then neither distributes nor tracks it. - The edit was accidental →
lacquer sync(orsync --forceto take the lacquer's version over yours).
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.
- 2d ago First seen · 211 lines · 109 tokens per session scan A f86955bb3ffa
working-with-lacquer is a skill published in the GitHub repository patrickserrano/lacquer (3 stars, last pushed 2d ago), licensed MIT. It adds 109 tokens to every session and 2,426 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
jk
Jenkins CLI for controllers. Use when users need to manage jobs, pipelines, config.xml, runs, logs, artifacts, credentials, nodes, or queues in Jenkins. Triggers include "jenkins", "jk", "pipeline", "build", "job create", "job config", "config.xml", "run logs", "jenkins credentials", "jenkins node".
github-actions
Use when adding CI/CD, creating workflows, auditing GitHub Actions, or fixing action pinning. Creates and audits workflows for SHA pinning and permissions.
github-issues
Use when filing a bug, requesting a feature, creating an issue, or updating issue details. Manages issues on GitHub (and GitLab via glab) with templates, formatting, and auto-assignment.
beads-schema
Beads (bd CLI) reference — issue types, statuses, priorities, dependencies, and common commands.
gitlab-cli
GitLab CLI (glab) wrapper for MR status, issues, and repository operations.