ref-brief

ref-brief is a skill for Claude Code, Codex from p4inz-code/3d-ref-skills. It costs 79 tokens per session (2,589 once invoked), scanned A, original, MIT.

A planning brief for gathering visual references before creating a 3D asset. It organizes what to research based on the asset, where it will be used, its visual style, and how closely it will be viewed.

In plain words
What is it for?
Use it before modeling a prop, character, vehicle, environment piece, weapon, or other 3D asset in tools such as Blender, Maya, ZBrush, 3ds Max, or Houdini.
Why use it?
Missing references can lead to modeling decisions being changed late, causing rework and delivery problems. A written brief gives the artist a shared target before modeling starts.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it before modeling a prop, character, vehicle, environment piece, weapon, or other 3D asset in tools such as Blender, Maya, ZBrush, 3ds Max, or Houdini.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/p4inz-code/3d-ref-skills/ref-brief
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 p4inz-code/3d-ref-skills --skill ref-brief
Clone the repo
git clone --depth 1 https://github.com/p4inz-code/3d-ref-skills

Made for: Claude Code, Codex.

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 ref-brief

README.md
[![agentmods](https://agentmods.dev/badge/skills/p4inz-code/3d-ref-skills/ref-brief/github.svg)](https://agentmods.dev/skills/p4inz-code/3d-ref-skills/ref-brief)
Your own site
<a href="https://agentmods.dev/skills/p4inz-code/3d-ref-skills/ref-brief"><img src="https://agentmods.dev/badge/skills/p4inz-code/3d-ref-skills/ref-brief/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 ref-brief

Your own site · 80×15
<a href="https://agentmods.dev/skills/p4inz-code/3d-ref-skills/ref-brief"><img src="https://agentmods.dev/badge/skills/p4inz-code/3d-ref-skills/ref-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 79 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,589 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.00079 $0.02589
Opus 5.5 $0.00032 $0.01036
Sonnet 5.5 $0.00016 $0.00518
Haiku 4.5 $0.00008 $0.00259

Measured 9d ago against content hash 9263a7991dc8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ref-brief 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/ref-brief/SKILL.md · 277 lines

How it starts

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

3D reference brief Generator

You are a senior 3D generalist with 10+ years across games, VFX, and marketplace publishing. You have shipped assets to AAA studios, sold on Fab, and built reference pipelines for production teams.

A bad reference brief leads to mid-model panic, wasted retopology, and assets that fail at delivery. A good one makes every modeling decision feel obvious.

Step 1: intake

Ask these four questions if not already clear from the prompt. Ask all at once:

  1. Asset type: What is it? (prop / hard surface / organic / character / environment piece / vehicle / creature / VFX element / modular kit / weapon / architecture)

  2. Target platform: Where is it going? (game real-time / Fab marketplace / film/VFX render / personal portfolio / archviz / mobile / web/WebGL)

  3. Art style: What is the visual direction? (realistic PBR / stylized / hand-painted / sci-fi / fantasy / toon / period/historical / low-poly / abstract)

  4. Camera distance: How close will the player/viewer get to this asset? (first-person: asset fills screen / third-person: 2-4m distance / isometric/RTS: seen from above at distance / cinematic: any distance / marketplace: close-up hero renders)

If the artist gives a description that answers all four implicitly, skip the questions and proceed directly to the brief.

Camera distance changes everything: poly budget, texel density, detail level, and which reference zones matter most. A first-person weapon needs 4× the detail of an RTS background prop at the same poly cost.

Step 2: generate the brief

Output the brief as a structured markdown document. Every section must be filled. Never write "N/A". If information is unknown, make a production-accurate assumption and label it as such.


Brief header

ASSET:            [name]
TYPE:             [classification]
PLATFORM:         [target]
STYLE:            [direction]
CAMERA DISTANCE:  [first-person / third-person / isometric / cinematic / marketplace]
POLY BUDGET:      [specific — e.g. "12k–18k tris LOD0 for FPS hero prop"]
                  [first-person: 8k–25k | third-person: 4k–12k | isometric: 1k–4k]
TEXEL DENSITY:    [specific — e.g. "512px/m hero, 256px/m background"]
                  [first-person: 512–1024px/m | third-person: 256–512px/m | iso: 128–256px/m]
DATE:             [today]

Read the full file on GitHub · 277 lines

Files

What ships with it

1 file 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 Changed 9263a7991dc8
  2. 1mo ago First seen · 277 lines · 79 tokens per session scan A 99c2a830d37f

Subscribe to this mod's changes

ref-brief is a skill published in the GitHub repository p4inz-code/3d-ref-skills (14 stars, last pushed 10d ago), licensed MIT. It adds 79 tokens to every session and 2,589 once invoked, about $0.0003 per session on Opus 5.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.