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 commands/patrickserrano/lacquer/testgit 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/commands/patrickserrano/lacquer/test)<a href="https://agentmods.dev/commands/patrickserrano/lacquer/test"><img src="https://agentmods.dev/badge/commands/patrickserrano/lacquer/test.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.00010 | $0.00327 |
| Opus 5 | $0.00005 | $0.00163 |
| Sonnet 5 | $0.00002 | $0.00065 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade A, and why
test 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 yesterday.
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
Run tests for {{PROJECT_NAME}} using flowdeck (see CLAUDE.md "Build & Test Tooling").
Arguments
$ARGUMENTS- Optional test filter (e.g., "Player", "Auth", "Settings")
Steps
-
Get a simulator UDID:
flowdeck simulator listPick an available iOS simulator and use its UDID — simulator names are ambiguous across OS versions, so never pass a name.
-
Run tests:
flowdeck test -w {{XCODEPROJ}} -s {{SCHEME}} -S <udid> -d {{COMPONENT_PREFIX}}DerivedData- If no argument: run the command above as-is (all tests).
- If
$ARGUMENTSis provided: append--only <TargetName>/<ClassName>(or--test-targets <name>to scope to a whole test target) to run just that module's tests. Seeflowdeck test --helpfor the exact selection format.
-
Parse test results and report:
- Total tests run
- Passed/failed count
- Failed test names with file locations
On Failure
For each failing test:
- Report the test name and failure reason
- Include file path and line number
- Suggest investigation approach (do NOT auto-fix)
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.
- yesterday First seen · 42 lines · 10 tokens per session scan A 770de2ef649a
test is a command published in the GitHub repository patrickserrano/lacquer (3 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 327 once invoked, about $0.0001 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 commands, from other repositories
instrument
Generate a comprehensive instrumentation plan for a mobile codebase.
mobile-verify
Run automated verification loops with pass@k metrics for mobile testing. Executes tests multiple times to detect flakiness.
feature-build
Build a complete mobile feature from description to running code with E2E tests. Orchestrates 6 phases - planning, implementation, testing, build-fix, quality gate, and verification. Auto-detects platform.
feature-plan
Plan a mobile feature with architecture decisions, file breakdown, dependency analysis, and test strategy. Produces a structured plan document reviewed by an architecture agent.
feature-status
Show the current status of a feature build - which phase is active, what has completed, what remains, and any blockers.
android-build
Build Android project with Gradle, fix errors, generate APK/AAB. Invokes android-build-resolver for issues.