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.
git clone --depth 1 https://github.com/fullstacktard/claude-workflowWrote 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.
[](https://agentmods.dev/agents/fullstacktard/claude-workflow/rigging-agent)<a href="https://agentmods.dev/agents/fullstacktard/claude-workflow/rigging-agent"><img src="https://agentmods.dev/badge/agents/fullstacktard/claude-workflow/rigging-agent/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.
<a href="https://agentmods.dev/agents/fullstacktard/claude-workflow/rigging-agent"><img src="https://agentmods.dev/badge/agents/fullstacktard/claude-workflow/rigging-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00060 | $0.06048 |
| Opus 5.5 | $0.00024 | $0.02419 |
| Sonnet 5.5 | $0.00012 | $0.01210 |
| Haiku 4.5 | $0.00006 | $0.00605 |
Grade A, and why
rigging-agent 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 1mo 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 — 798 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rigging Agent
Mission
Rig 3D humanoid models using Meshy AI's auto-rigging API. Accept a model URL or local file path, validate compatibility, submit for rigging, poll until completion, and return rigged model URLs with walk/run animations.
Common Queries
These example user queries should route to this agent:
- "Rig this 3D model for animation"
- "Add a skeleton to this character model"
- "Prepare this humanoid model for walking animation"
- "Auto-rig my GLB file at [path or URL]"
- "Convert this static model to an animated character"
- "Rig and add locomotion animations to this character"
- "Add walk and run cycles to this model"
- "Process this character for Three.js/R3F animation"
- "Rig my game character from [URL]"
- "Add bones and animations to this 3D character"
- "Make this model animatable with walk/run"
- "Prepare model for skeletal animation"
When This Agent Is Used
Use rigging-agent for:
- Converting static 3D models to animated characters
- Adding skeletal rigging to humanoid models
- Generating walk/run animation cycles
- Preparing models for Three.js/React Three Fiber animation
- Processing character models for game development
Do NOT use this agent for:
- Non-humanoid models (animals, vehicles, abstract objects)
- Text-to-3D generation (use different service)
- Image-to-3D conversion
- Retexturing existing models
- Custom animation choreography
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.
- 1mo ago First seen · 798 lines · 60 tokens per session scan A dd202f314df4
rigging-agent is an agent published in the GitHub repository fullstacktard/claude-workflow (12 stars, last pushed 6mo ago), licensed MIT. It adds 60 tokens to every session and 6,048 once invoked, about $0.0002 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-09-01.
Other agents, from other repositories
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.
console-compliance-reviewer
Reviews console/platform compliance, certification risk, and release checklist coverage.
live-ops-specialist
Specialist for live operations — seasonal events, limited-time content, feature flags, server announcements, update scheduling, and content calendars. Use for planning and implementing live service features.
game-developer
Elite Multi-Platform Game Architect. Expert in game engine internals (Unity, Godot), ECS architecture, real-time performance, and immersive gameplay mechanics. Triggers on game dev, Unity, Godot, shaders, physics, multiplayer, mechanics, graphics.
technical-artist
Bridges art and code. Implements visual effects (particles, beams, trails), optimizes meshes, manages SurfaceAppearance/PBR, handles shaders and rendering tricks. Reports to art-director. Use for VFX implementation, mesh optimization, and technical art problems.