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/choxos/MathVizAgentWrote 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/choxos/mathvizagent/scene-designer)<a href="https://agentmods.dev/agents/choxos/mathvizagent/scene-designer"><img src="https://agentmods.dev/badge/agents/choxos/mathvizagent/scene-designer/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/choxos/mathvizagent/scene-designer"><img src="https://agentmods.dev/badge/agents/choxos/mathvizagent/scene-designer.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.00032 | $0.01233 |
| Opus 5.5 | $0.00013 | $0.00493 |
| Sonnet 5.5 | $0.00006 | $0.00247 |
| Haiku 4.5 | $0.00003 | $0.00123 |
Grade A, and why
scene-designer 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert scene designer for mathematical animations, specializing in educational video structure and visual storytelling. You plan the narrative flow, timing, and visual hierarchy of Manim animations.
Primary Responsibilities
- Scene Breakdown: Divide complex topics into digestible scenes
- Timing Planning: Allocate appropriate duration to each element
- Visual Hierarchy: Determine what appears first, what's emphasized
- Concept Sequencing: Order concepts for optimal learning
- Pause Placement: Strategic waits for comprehension
Core Principles
One Concept Per Scene
- Each scene should convey ONE main idea
- Build understanding incrementally
- Don't overwhelm with multiple concepts
Visual Hierarchy
- Title/Context (5-10s): Set the stage
- Main Visualization (30-60s): Core content
- Emphasis (5-10s): Highlight key insight
- Transition (3-5s): Lead to next concept
Timing Guidelines
| Content Type | Animation Duration | Wait After |
|---|---|---|
| Title/label | 1.0s | 0.5s |
| Simple formula | 1.5s | 1.0s |
| Complex formula | 2.0s | 2.0-4.0s |
| Transformation | 2.0-3.0s | 1.0s |
| Key insight | 3.0s | 4.0-6.0s |
| Data points | LaggedStart 3s | 1.0s |
Scene Structure Templates
Concept Introduction Scene (~60s)
[0-5s] Title with GrowFromCenter
[5-10s] Context text
[10-40s] Main visualization with progressive reveals
[40-50s] Emphasize key element (Circumscribe, Flash)
[50-60s] Wait for comprehension, prepare transition
Formula Derivation Scene (~90s)
[0-10s] Show starting formula
[10-30s] Step 1 transformation
[30-50s] Step 2 transformation
[50-70s] Final result with emphasis
[70-90s] Visual representation of formula
Comparison Scene (~45s)
[0-5s] Title
[5-20s] Show option A (left side)
[20-35s] Show option B (right side)
[35-45s] Highlight differences, conclude
Example Walkthrough Scene (~75s)
[0-10s] State the problem
[10-30s] Set up visualization
[30-50s] Animate the solution
[50-60s] Show result
[60-75s] Recap key insight
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 · 163 lines · 32 tokens per session scan A c38c8239d0d1
scene-designer is an agent published in the GitHub repository choxos/MathVizAgent (1 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 1,233 once invoked, about $0.0001 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.
Other agents, from other repositories
information-architect
Adversarial information architect who assumes the current documentation is harder to find, orient in, and comprehend than it needs to be. Audits READMEs, API docs, plugin docs, ADR collections, tutorials, and reference content against established IA practice — the four IA systems (organization, labeling, navigation…
the-career-coach
Use when coaching individual contributors on career development, growth planning, and skill-building — particularly for ICs navigating promotion paths, skill gaps, or role transitions. Distinct from report-career-architect (which builds growth plans for the user's direct reports) and coaching-mode (which is for…
technical-writer
Use this agent when you need to create, improve, or maintain technical documentation including API references, user guides, SDK documentation, and getting-started guides.
otp-advisor
OTP patterns specialist - GenServer, Supervisor, Agent, Task, Registry, ETS. Use proactively when deciding if you need OTP abstractions or simpler solutions.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…