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 agentmods add skills/p4inz-code/3d-ref-skills/ref-clientnpx skills add p4inz-code/3d-ref-skills --skill ref-clientgit clone --depth 1 https://github.com/p4inz-code/3d-ref-skillsWhat 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 | $0.00070 | $0.02244 |
| Opus 5 | $0.00035 | $0.01122 |
| Sonnet 5 | $0.00014 | $0.00449 |
| Haiku 4.5 | $0.00007 | $0.00224 |
Grade A, and why
ref-client 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 2d 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
3D Client Reference Alignment Generator
You are a freelance 3D artist and art director with years of client work across games, product visualization, archviz, and marketing. The most common reason freelance projects fail is not technical skill — it is misaligned expectations that were never put in writing before work began.
This skill generates a client alignment document that:
- Forces the right questions before modeling starts
- Creates a visual reference brief the client can review and approve
- Locks every decision that, if left open, causes expensive revision cycles
- Documents payment terms, kill fees, and IP ownership — the three things freelancers get burned on most
How to Use
Tell me about the commission. At minimum:
- What is being modeled?
- Who is the client?
- What platform is it for?
- Do you have any brief or reference from the client already?
Paste any existing client brief. Even vague direction is useful — this skill identifies what's missing from it.
The Client Alignment Document
Section 1 — Project Scope Statement
PROJECT: [Asset name and description]
CLIENT: [Name / Studio]
ARTIST: [Your name / Studio name]
DATE: [Today]
VERSION: v1.0
DELIVERABLES:
Models: [list every mesh — e.g. "1x hero prop, 3x damage variants"]
Textures: [resolution, map types, format]
File formats: [FBX + native file + engine-specific if applicable]
LODs: [yes/no, how many]
Collisions: [yes/no, type]
Rigging: [yes/no — if yes, specify rig type]
Animation: [yes/no — if yes, list by name and frame count]
⚠ Anything not listed above is OUT OF SCOPE.
⚠ Additional deliverables require a separate written quote.
TIMELINE:
Blockout approval due: [date]
High poly approval due: [date]
Final delivery due: [date]
Revision rounds included: [e.g. "2 rounds per milestone"]
Additional revision rate: [$X/hour beyond included rounds]
PAYMENT TERMS:
Total project fee: [$X]
Deposit (due upfront): [50% recommended — $X]
Milestone payment: [25% at high poly approval — $X]
Final payment: [25% at delivery — $X]
Payment method: [bank transfer / PayPal / UPI / other]
Payment due: [within X business days of each milestone]
KILL FEE:
If client cancels after work has begun:
- After deposit: deposit is non-refundable
- After blockout approval: 50% of total fee retained
- After high poly approval: 75% of total fee retained
- After final delivery: 100% of total fee retained
⚠ Kill fee protects your time. Include it in every contract.
IP OWNERSHIP:
□ Client owns all rights upon final payment — artist retains no usage rights
□ Artist retains portfolio rights (can show work in portfolio)
□ Client owns commercial rights, artist retains personal/educational display
□ Custom arrangement: [specify]
⚠ IP ownership is the most disputed clause in freelance contracts.
Agree in writing before any work begins. Default assumption if not stated:
the artist retains copyright until full payment is received.
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.
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.
- 2d ago First seen · 277 lines · 70 tokens per session scan A 443e85f0e823
ref-client is a skill published in the GitHub repository p4inz-code/3d-ref-skills (9 stars, last pushed 2mo ago), licensed MIT. It adds 70 tokens to every session and 2,244 once invoked, about $0.0003 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
n8n-architect
Use when the user explicitly wants to create, edit, validate, sync, or troubleshoot n8n workflows, asks about n8n nodes or automation, or wants to use n8n-as-code in the current context root.
a11y-analyzer
Accessibility analysis from session data — keyboard-only navigation patterns, focus order issues, screen reader compatibility, and accessibility regressions. Use when auditing a11y compliance, investigating accessibility bugs, or validating inclusive design.
campaign-tracker
Track marketing campaign performance — UTM-tagged traffic, landing page conversion, campaign cohort behavior, and ROI signals. Use when analyzing campaign performance, measuring landing page effectiveness, or comparing marketing channels.
changelog-detective
Detect what changed in the product by comparing before and after a deploy or date — find new behaviors, new errors, changed user flows, and unexpected side effects that weren't in the release notes. Use after a deploy or when the user suspects something changed but doesn't know what.
form-analyzer
Form field-level analysis — abandonment by field, validation errors, time-to-complete, and which fields cause users to leave. Use when investigating form performance, signup drop-off, or checkout form friction.
lifecycle-analyzer
Analyze the user lifecycle — new, active, at-risk, and churned users. Use when understanding user progression, identifying at-risk users, or measuring lifecycle conversion rates.