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 skills add vinsonconsulting/limner --skill brand-stampgit 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/brand-stamp)<a href="https://agentmods.dev/skills/vinsonconsulting/limner/brand-stamp"><img src="https://agentmods.dev/badge/skills/vinsonconsulting/limner/brand-stamp.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.01174 |
| Opus 5 | $0.00021 | $0.00587 |
| Sonnet 5 | $0.00008 | $0.00235 |
| Haiku 4.5 | $0.00004 | $0.00117 |
Grade A, and why
brand-stamp 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 8d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brand stamp and watermark
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 put a logo or watermark onto a finished image. Compose's watermark op composites one image onto another at a pixel offset; it has no opacity, scale, or tiling knob, so you size and fade the mark yourself before compositing. The reference at the end gives the op's fields and the placement math.
Procedure
- Get the mark ready. Use a logo on a transparent background, or render watermark text first with the renderText op onto a transparent canvas.
- Size the mark. The op places the overlay as-is, so resize it first (the compose resize op) to a small fraction of the base; a corner mark is usually 10 to 20 percent of the width.
- Compute the position. Position is a pixel offset from the top-left, so derive the corner from the sizes: bottom-right is (baseWidth minus overlayWidth minus margin, baseHeight minus overlayHeight minus margin).
- Composite. Call compose with the watermark op (base, overlay, x, y). The mark's transparent areas let the base show through.
- Fade if asked. The op takes no opacity value, so bake reduced opacity into the mark before compositing; on Workers you can instead use the Cloudflare Images draw layer's opacity.
- Deliver one asset. Convert to JPEG or WebP if file size matters, then return the result through its capability URL.
Judgment
- Keep the mark small and in a consistent corner across a set so it reads as a stamp, not a focal point.
- Prefer a transparent-background logo; a mark with a solid box around it fights the image underneath.
- For a faded look, bake the alpha into the mark in local runs; reserve the Cloudflare opacity path for Workers, where the Images binding exists.
- The op stamps the mark once. It does not tile a repeated pattern.
Reference
The table below is generated from the Limner guidance core (@limner/core), the
same source the MCP brand-stamp prompt serves, so this skill and that prompt
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.
- 8d ago First seen · 89 lines · 42 tokens per session scan A dffc3975d0b7
brand-stamp is a skill published in the GitHub repository vinsonconsulting/limner (1 stars, last pushed 27d ago), licensed Apache-2.0. It adds 42 tokens to every session and 1,174 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.