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 art-researchgit 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/art-research)<a href="https://agentmods.dev/skills/vinsonconsulting/limner/art-research"><img src="https://agentmods.dev/badge/skills/vinsonconsulting/limner/art-research/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/vinsonconsulting/limner/art-research"><img src="https://agentmods.dev/badge/skills/vinsonconsulting/limner/art-research.svg" alt="Reviewed on agentmods" width="80" 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.00043 | $0.00921 |
| Opus 5 | $0.00022 | $0.00461 |
| Sonnet 5 | $0.00009 | $0.00184 |
| Haiku 4.5 | $0.00004 | $0.00092 |
Grade A, and why
art-research 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Art research
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 turn a question about a style, movement, or technique into visual direction. Research it with your web tools, distill what defines the look, and write it to the project's style profile so the research steers every prompt that follows. This is the research-to-generation loop applied to art history. The reference at the end states the profile shape and the rules.
Procedure
- Research the style. Use your web tools to find its period and origin, palette, signature motifs and composition, medium, and a few exemplar works or artists. Prefer primary or authoritative sources.
- Know when to stop. This is a single research pass, not a fleet; stop once you can name the palette, the medium, and three or four signature traits.
- Distill into a profile. Write the findings to the style profile with upsertStyleProfile: palette, descriptors, medium. Set provenance.source to art-research and note the key sources.
- Record exemplars. List exemplar works under references (kind url or note).
- Generate from the research. Shape each prompt from the profile's descriptors and medium, and set pipelinePrefs for the pipeline that best renders the style.
Judgment
- Stop at the point of diminishing returns: palette, medium, and a few signature traits are enough to steer prompts.
- Keep descriptors concrete and few; a tight profile generates more consistently than a long one.
- Match the pipeline to the medium: vector work to Recraft, painterly work to Midjourney or DALL·E.
- The profile is shared, so research done here can seed a brand kit or pair with style-from-images.
Reference
The text below is generated from the Limner guidance core (@limner/core), the
same source the related MCP surfaces serve, so this skill cannot drift from it.
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 · 73 lines · 43 tokens per session scan A 062d6daf657e
art-research is a skill published in the GitHub repository vinsonconsulting/limner (1 stars, last pushed 27d ago), licensed Apache-2.0. It adds 43 tokens to every session and 921 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.