articraft-authoring

articraft-authoring is a skill for Claude Code, Codex from mattzh72/articraft. It costs 28 tokens per session (914 once invoked), scanned A, original, Apache-2.0.

An authoring workflow for creating, editing, checking, and finalizing Articraft articulated-object records in a local library. It supports managed generation, no-key Codex generation, and explicitly requested external authoring.

In plain words
What is it for?
Use it when producing or repairing an Articraft asset or record, choosing the appropriate generation mode and validating the result through Articraft's tools.
Why use it?
It keeps records, metadata, traces, and run details consistent with Articraft's required process instead of assembling them manually.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Codex.

Good fit Use it when producing or repairing an Articraft asset or record, choosing the appropriate generation mode and validating the result through Articraft's tools.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mattzh72/articraft/articraft-authoring
About the project

Articraft is a toolset for generating, viewing, and working with articulated 3D assets from text prompts. Researchers and developers use its generation code, viewer, SDK, command-line tools, and dataset; the repository points current development to a successor project.

mattzh72/articraft · 1,495 stars · on GitHub

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 mattzh72/articraft --skill articraft-authoring
Clone the repo
git clone --depth 1 https://github.com/mattzh72/articraft

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 articraft-authoring

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/mattzh72/articraft/articraft-authoring"><img src="https://agentmods.dev/badge/skills/mattzh72/articraft/articraft-authoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 914 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00028 $0.00914
Opus 5 $0.00014 $0.00457
Sonnet 5 $0.00006 $0.00183
Haiku 4.5 $0.00003 $0.00091

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

Security

Grade A, and why

articraft-authoring 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 13d 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.

plugins/articraft/skills/articraft-authoring/SKILL.md · 126 lines

How it starts

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

Articraft Authoring

Use this skill when the user asks Codex to create, edit, fix, improve, check, or finalize an Articraft asset or record.

Core Rule

There are three supported Articraft authoring modes. Choose the mode from the user's request before creating a record.

  • Use native Articraft generation when the user needs Articraft-managed run metadata, cost accounting, turn counts, or the full agent trajectory. This path requires the relevant provider API key.
  • Use no-key Codex generation when the user wants Codex access without provider API keys. This path uses --provider codex-cli inside Articraft's internal harness, so Articraft still owns the loop, tools, compile feedback, turn counts, compile-attempt counts, record persistence, and trajectory.
  • Use external Codex authoring only when the user explicitly asks Codex to manually edit model.py outside the internal harness. This path creates an external-agent record and intentionally has no Articraft internal trace.

Never manually create record directories, invent record metadata, copy record folders, write traces, or bypass the CLI.

Read the repository contract before external authoring:

sed -n '1,220p' EXTERNAL_AGENT_DATA.md

Also read the core quality requirements before writing geometry:

agent/prompts/sections/designer_common.md
agent/prompts/sections/link_naming.md

Use SDK docs and examples while authoring:

sdk/_docs/
sdk/_examples/

Setup

From the Articraft repo root:

uv sync --group dev
uv run articraft init

If the user wants a specific data folder, pass --data-dir or set ARTICRAFT_DATA_DIR.

Create A New Record

For a full Articraft run with cost, turn count, and trajectory, use native generation:

uv run articraft generate "<prompt>"

For no-key Codex generation with Articraft loop parity, use the Codex CLI provider:

uv run articraft generate --provider codex-cli --model <codex-model-id> "<prompt>"

For image-conditioned no-key Codex generation:

Read the full file on GitHub · 126 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. 13d ago First seen · 126 lines · 28 tokens per session scan A aee66c814ec5

Subscribe to this mod's changes

articraft-authoring is a skill published in the GitHub repository mattzh72/articraft (1,495 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 28 tokens to every session and 914 once invoked, about $0.0001 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens