vinci

vinci is a skill for Claude Code, Codex from mbanderas/maestro-vinci. It costs 89 tokens per session (1,352 once invoked), scanned A, original, MIT.

A design skill for creating and reviewing visual work for websites, apps, prototypes, design systems, presentations, reports, brands, and campaigns.

In plain words
What is it for?
It is for shaping creative direction, visual identities, interface concepts, design specifications, tokens, mockups, and concrete design feedback.
Why use it?
It provides a structured way to make design decisions and critique existing work while considering the project's own visual rules and constraints.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the maestro-vinci plugin — 1 skill shipped together

Good fit It is for shaping creative direction, visual identities, interface concepts, design specifications, tokens, mockups, and concrete design feedback.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mbanderas/maestro-vinci/vinci
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 mbanderas/maestro-vinci --skill vinci
Clone the repo
git clone --depth 1 https://github.com/mbanderas/maestro-vinci

Made for: Claude Code, Codex.

Or install maestro-vinci, the plugin that ships this one along with the rest of its 1 skill.

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 vinci

README.md
[![agentmods](https://agentmods.dev/badge/skills/mbanderas/maestro-vinci/vinci/github.svg)](https://agentmods.dev/skills/mbanderas/maestro-vinci/vinci)
Your own site
<a href="https://agentmods.dev/skills/mbanderas/maestro-vinci/vinci"><img src="https://agentmods.dev/badge/skills/mbanderas/maestro-vinci/vinci/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 vinci

Your own site · 80×15
<a href="https://agentmods.dev/skills/mbanderas/maestro-vinci/vinci"><img src="https://agentmods.dev/badge/skills/mbanderas/maestro-vinci/vinci.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 89 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,352 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.00089 $0.01352
Opus 5 $0.00044 $0.00676
Sonnet 5 $0.00018 $0.00270
Haiku 4.5 $0.00009 $0.00135

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

Security

Grade A, and why

vinci 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 9d 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/vinci/SKILL.md · 101 lines

How it starts

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

Maestro: Vinci

Operate as a design polymath inside the user's current repository. Resolve every relative path in this file from the vinci skill directory. Preserve the target repository's stack, product truth, instructions, and publication boundaries.

Apply authority in order

  1. Follow the user's current request and the target repository's instructions.
  2. Follow this runtime adapter.
  3. Read references/persona.md for identity, scope, judgment, and boundaries.
  4. Read references/design-doctrine.md and only the relevant chapter under references/craft/doctrine/.
  5. Use target-project evidence before the bundled external catalog.

Do not turn a design request into production integration, deployment, backend work, broad research, or a framework migration unless the user explicitly includes that work.

Start every task

  1. Read applicable target-repository instructions, design-system documentation, tokens, components, and shipped same-type surfaces.
  2. Classify the mode:
    • normal: create a mock, visual artifact, design specification, tokens, deck, report, or brand asset;
    • critique: inspect existing work and return ranked, concrete findings;
    • consultation: answer a bounded design question;
    • brief-extraction: produce a complete brief when missing audience, purpose, voice, or constraints would materially change the result.
  3. Classify change scope separately: targeted-edit, extension, new-artifact, redesign, or critique-only. Keep targeted work targeted.
  4. Infer the target medium and stack from the request and repository. Retain the incumbent framework and component system.
  5. Read references/persona.md. For authoring or critique, also read references/design-doctrine.md.
  6. Load only task-relevant craft chapters. Use references/craft/doctrine/README.md as the index. Always include chapters 01, 03, and 18 for a new artifact or redesign.
  7. For an extension, new artifact, redesign, or critique, read references/design-operations.md. For rendered interfaces, read references/interface-evaluation.md before the final pass.

Read the full file on GitHub · 101 lines

Files

What ships with it

33 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 9d ago First seen · 101 lines · 89 tokens per session scan A 31ee83c11199

Subscribe to this mod's changes

vinci is a skill published in the GitHub repository mbanderas/maestro-vinci (2 stars, last pushed 28d ago), licensed MIT. It adds 89 tokens to every session and 1,352 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

figma-extract-design-system

Extract a design system from vibe-coded production apps that never had one: inventory components, mine de-facto styling into DTCG tokens, scaffold a Storybook package, port components, and optionally round-trip tokens/components into Figma. Use when the user wants to 'extract a design system', 'create a design system…

southleft/figma-console-mcp-skills · 133 tokens

figma-version-history

List a Figma file's version history, snapshot the file at any past version, and diff two versions (added/removed/renamed pages plus deep per-component changes). Use when the user wants to inspect Figma history — triggers: 'list Figma versions', 'what versions does this file have', 'show version history', 'snapshot…

southleft/figma-console-mcp-skills · 181 tokens

figma-blame-node

Find which Figma version introduced a specific change — a component property or a child node — via a binary search over version history (log2(N) API calls instead of N). Answers 'who added this and when'. Use when the user wants git-blame-style attribution for a Figma design — triggers: 'when was this component…

southleft/figma-console-mcp-skills · 176 tokens

figma-comments

Read, post, reply to, and delete comments on a Figma file via the REST API — including pinning a comment to a specific node and threading replies. Use when the user wants to work with Figma comments programmatically — triggers: 'get Figma comments', 'read comments on this file', 'post a comment in Figma', 'leave a…

southleft/figma-console-mcp-skills · 151 tokens

figma-export-tokens

Export Figma variables to design token files in DTCG, CSS custom properties, Tailwind v4/v3, SCSS, TypeScript, JSON, Style Dictionary, or Tokens Studio. Use when the user wants to pull design tokens OUT of Figma into code — triggers: 'export tokens', 'export Figma variables', 'generate CSS variables from Figma', 'turn…

southleft/figma-console-mcp-skills · 144 tokens

figma-generate-component-doc

Generate complete Markdown documentation for a Figma component — anatomy/layer tree, design tokens (colors, spacing, typography), states/variants matrix, accessibility notes, content guidelines, and optional code-parity + YAML frontmatter. Use when the user wants a docs page or handoff spec for a component or…

southleft/figma-console-mcp-skills · 150 tokens