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 skills/patrickserrano/lacquer/exploring-an-ideanpx skills add patrickserrano/lacquer --skill exploring-an-ideagit 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/skills/patrickserrano/lacquer/exploring-an-idea)<a href="https://agentmods.dev/skills/patrickserrano/lacquer/exploring-an-idea"><img src="https://agentmods.dev/badge/skills/patrickserrano/lacquer/exploring-an-idea.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.00106 | $0.02065 |
| Opus 5 | $0.00053 | $0.01033 |
| Sonnet 5 | $0.00021 | $0.00413 |
| Haiku 4.5 | $0.00011 | $0.00206 |
Grade A, and why
exploring-an-idea scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
The Needledrop probes would have been: one `curl` with Spotify client How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exploring an Idea
A design document reads as settled fact whether or not anyone checked. That is the whole failure mode: an unverified sentence in a PCD becomes an interface, then a dependency, then a week of work, and nothing in the process ever asks "how do we know that?"
This skill exists to put that question before the document instead of after it.
The case this was written from
Needledrop (NFC tap-to-stream for record collectors) had an unusually good PRD and PCD — real non-goals, numeric kill criteria, a named Phase 0 with exit criteria. It still shipped four false premises into its architecture, and the Phase 0 spike had to correct all four:
| The PCD asserted | Measurement found |
|---|---|
| "Spotify is effectively closed to us" (5-user dev cap, 250k-MAU quota wall) | Those gate user-data endpoints. Client credentials reach /v1/search and /v1/albums today. Spotify became the best-covered platform. |
| Barcode/UPC is the strongest identifier — "UPC preferred" | Discogs carries the physical pressing's barcode; streaming keys the digital release UPC. Different numbers. Spotify UPC lookups hit 0/46, Apple 5/42. |
| Odesli is the hedge for the Spotify gap | Odesli returned 0 Spotify links in 19 Apple-seeded album responses. It could not be the hedge. |
| Apple Music needs a MusicKit credential | Keyless for UPC and tracklist lookup. |
None of these were sloppy. Each is a plausible reading of vendor documentation. They were wrong anyway, and the cost was concrete:
- An entire provider-abstraction layer —
LinkResolver, capabilitiesOptionSet, chain-of-resolvers — designed around swapping away from a dependency that turned out to be unnecessary. - A "blocking, business" open question (email Odesli for commercial terms, owner assigned, week 1) generated by a gap that did not exist.
- A long "Option D — build our own resolver" analysis premised on Spotify being unreachable.
- The real finding — tracklist matching, which took the album shelf from 62.1% to 79.3% and Spotify from 0% to 60% — appears nowhere in the PCD, because the document had already decided the identifier ladder.
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.
- 4d ago First seen · 167 lines · 106 tokens per session scan A ce32d074e6d1
exploring-an-idea is a skill published in the GitHub repository patrickserrano/lacquer (3 stars, last pushed today), licensed MIT. It adds 106 tokens to every session and 2,065 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
opik
This skill should be used when the user needs to add Opik tracing or integrations to their code, instrument an LLM application, or needs reference for Opik SDK usage (Python, TypeScript, REST API). Use for tasks like "add tracing", "instrument my code", "use trackopenai", "add OpikTracer", "what span types are…
ollama-review
Get a second opinion from a local Ollama LLM on your current code changes. Analyzes staged/unstaged diffs and returns prioritized findings. No API keys needed. Use when user asks to "review with Ollama", "local code review", or "review offline".
mcp-builder
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
swarm
Run a multi-agent audit of a codebase by spawning specialized parallel subagents (security, performance, tests, architecture, dead-code), then synthesize their findings into a single prioritized action plan. Use this whenever the user runs /swarm, asks to "audit the repo," "review this codebase," "find issues across…
hyper-plan
Use when about to start a non-trivial implementation that needs decomposition before coding. Also when the user invokes /hyperclaude:hyper-plan. Produces an ordered, bite-sized plan in .hyperclaude/plans/ — the input for /hyperclaude:hyper-plan-review and /hyperclaude:hyper-implement.
hyper-docs-review
Use after documentation edits — typically after the documenter agent runs, or when the user invokes /hyperclaude:hyper-docs-review. Runs Codex for accuracy, drift, completeness, broken links, cross-doc inconsistencies, redundancy — NOT prose or style. Distinct from /hyperclaude:hyper-code-review (code diffs) and…