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/vinsonconsulting/limner/print-readynpx skills add vinsonconsulting/limner --skill print-readygit clone --depth 1 https://github.com/vinsonconsulting/limnerWrote 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/vinsonconsulting/limner/print-ready)<a href="https://agentmods.dev/skills/vinsonconsulting/limner/print-ready"><img src="https://agentmods.dev/badge/skills/vinsonconsulting/limner/print-ready.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.00042 | $0.01069 |
| Opus 5 | $0.00021 | $0.00535 |
| Sonnet 5 | $0.00008 | $0.00214 |
| Haiku 4.5 | $0.00004 | $0.00107 |
Grade A, and why
print-ready 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 5d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Print-ready export
Limner is an independent third-party project built on Anthropic's CMA platform; it is not an Anthropic or Claude product.
Use this skill to take a finished asset toward print. Limner generates an RGB raster and enlarges it to print resolution; the press-specific steps (CMYK color, bleed, and containers like TIFF or PDF/X) are a handoff to a desktop print tool. This skill covers the Limner side and where it hands off. The reference at the end gives the resolution math and the step-by-step ownership.
Procedure
- Confirm the printer's requirements: final size, resolution, color profile, bleed, and file format. These set everything that follows.
- Compute the pixel size: print size in inches times 300 dpi (a 5 by 7 inch print needs about 1500 by 2100 px).
- Upscale to that size. Use limner_upscale to enlarge the finished raster toward print resolution, while it is still the working asset. For a flat logo, vectorize it instead, since a vector stays sharp at any size.
- Hand off for CMYK and export. Limner stays in RGB and does not write press containers, so pass the upscaled asset to a desktop editor (Affinity Photo or Publisher, or GIMP) for CMYK conversion, soft-proofing, bleed, and export to TIFF or PDF/X.
- Deliver the working asset. Return the upscaled RGB asset through its capability URL so the print tool has a clean, high-resolution source.
Judgment
- Upscale before color conversion and export, while the asset is still a working raster.
- Vectorize flat marks instead of upscaling them; a vector needs no resolution.
- Limner does not do CMYK or PDF/X. Do not promise a press-ready file from Limner alone; the CMYK and container steps are the handoff.
- Confirm the printer's color profile and bleed up front. They change the export, not the Limner steps.
Reference
The text below is generated from the Limner guidance core (@limner/core), the
same source the MCP print-ready resource serves, so this skill and that resource
cannot drift. Do not edit the generated region by hand; run
pnpm --filter @limner/limner-agent gen:skills instead.
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.
- 5d ago First seen · 81 lines · 42 tokens per session scan A f27dff9ebb9f
print-ready is a skill published in the GitHub repository vinsonconsulting/limner (1 stars, last pushed 24d ago), licensed Apache-2.0. It adds 42 tokens to every session and 1,069 once invoked, about $0.0002 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 skills, from other repositories
flux-3-product-ads
Use when building a finished product ad from FLUX 3 - shot design, voiceover, action-to-word sync, evidence-gated copy, deterministic assembly, and QC gates that catch clipped audio, floating products, off-model plates, and reports that claim a pass the build did not give.
bfl-api
BFL FLUX API integration guide covering endpoints, async polling patterns, rate limiting, error handling, webhooks, and regional endpoints with Python and TypeScript code examples.
flux-3-archival-formats
Use when a FLUX 3 video needs a period or archival look. Covers naming a recording format instead of a mood, per-format artifacts, and templates.
flux-image-best-practices
Comprehensive guide for BFL FLUX image generation models. Covers prompting, T2I, I2I, structured JSON, hex colors, typography, multi-reference editing, and model-specific best practices for FLUX.2 and FLUX.1 families.
flux-3-keyframes-continuation
Use when a FLUX 3 video must be built from supplied images or video. Covers keyframes (i2v) and continuation (v2v).
flux-3-prompt-doctor
Use when diagnosing a FLUX 3 brief before generation. Resolve missing, conflicting, or schema-changing requirements.