apply-watercolor-technique

apply-watercolor-technique is a skill for Claude Code from jeffreytse/grimoire-core. It costs 44 tokens per session (1,482 once invoked), scanned A, original, MIT.

A guide to watercolor painting techniques, including how much water and pigment to use, when to paint on wet or dry paper, and how to build transparent layers.

In plain words
What is it for?
Planning watercolor layers, choosing wet-on-wet or wet-on-dry methods, preserving white paper, and creating clear, glowing washes.
Why use it?
It helps prevent muddy colors and protects the light areas that watercolor usually cannot easily restore once covered.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the grimoire-art plugin — 18 skills shipped together

Good fit Planning watercolor layers, choosing wet-on-wet or wet-on-dry methods, preserving white paper, and creating clear, glowing washes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeffreytse/grimoire-core/apply-watercolor-technique
Install

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.

Any agent
npx skills add jeffreytse/grimoire-core --skill apply-watercolor-technique
Clone the repo
git clone --depth 1 https://github.com/jeffreytse/grimoire-core

Made for: Claude Code.

Or install grimoire-art, the plugin that ships this one along with the rest of its 18 skills.

Wrote 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.

agentmods badge for apply-watercolor-technique

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-watercolor-technique/github.svg)](https://agentmods.dev/skills/jeffreytse/grimoire-core/apply-watercolor-technique)
Your own site
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/apply-watercolor-technique"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-watercolor-technique/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.

agentmods 80×15 button for apply-watercolor-technique

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/apply-watercolor-technique"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-watercolor-technique.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,482 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.01482
Opus 5 $0.00022 $0.00741
Sonnet 5 $0.00009 $0.00296
Haiku 4.5 $0.00004 $0.00148

Measured 11d ago against content hash 0b53afbcff6d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

apply-watercolor-technique 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 11d 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.

skills/art/painting/skills/apply-watercolor-technique/SKILL.md · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Apply Watercolor Technique

Produce luminous watercolor paintings by controlling pigment-to-water ratio, choosing wet-on-wet vs wet-on-dry deliberately, preserving whites from the start, and building glazed layers from light to dark.

Why This Is Best Practice

Adopted by: John Singer Sargent's watercolors (now in major museum collections worldwide) exemplify the wet-on-wet/wet-on-dry control that watercolor mastery requires. The Royal Watercolour Society and American Watercolor Society both define luminosity and transparency as the defining qualities of high watercolor. All professional watercolor instruction (National Watercolor Society workshops, Bockingford and Winsor & Newton educational materials) centers on water-to-pigment ratio control as the primary technical skill. Why best: Watercolor is unforgiving of rework — pigment can't be added as opaque white and dried layers can't be lifted without disturbing the surface, so the sequence (whites preserved first, light-to-dark glazing, deliberate wet-on-wet vs wet-on-dry choice) is the only path to luminous results rather than mud. Impact: The most common failure mode in watercolor is overworking — re-wetting dried layers disturbs the surface, lifts pigment, and creates muddy color. A painter who plans the light-to-dark sequence and preserves whites from the beginning avoids these failures entirely. Wet-on-wet produces the soft, atmospheric edges unique to watercolor; wet-on-dry produces the crisp, controlled edges that give definition. Using both intentionally produces paintings that neither oil nor digital can replicate.

Steps

1. Plan the painting before touching water — map whites

Watercolor is subtractive only: you cannot add white pigment and maintain transparency. All lights and whites must be preserved as unpainted paper.

Before mixing:

  1. Sketch lightly in pencil (HB or lighter — harder graphite stays visible and bleeds less)
  2. Map every light shape: sky holes in foliage, highlights on water, light on faces
  3. Decide: which whites are absolute (paper preserved) vs which will be lightened glazes

Read the full file on GitHub · 98 lines

Changes

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.

  1. 11d ago First seen · 98 lines · 44 tokens per session scan A 0b53afbcff6d

Subscribe to this mod's changes

apply-watercolor-technique is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 22d ago), licensed MIT. It adds 44 tokens to every session and 1,482 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.