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 commands/choxos/mathvizagent/create-videogit clone --depth 1 https://github.com/choxos/MathVizAgentWhat 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.00016 | $0.01588 |
| Opus 5 | $0.00008 | $0.00794 |
| Sonnet 5 | $0.00003 | $0.00318 |
| Haiku 4.5 | $0.00002 | $0.00159 |
Grade A, and why
create-video 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 yesterday.
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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/create-video - Multi-Scene Video Creation Workflow
Create a complete educational video with multiple scenes, consistent styling, and proper concatenation.
Workflow Steps
Step 1: Video Planning (@viz-architect)
Gather high-level requirements:
- Topic: Main subject of the video
- Target Audience: Beginner / Intermediate / Advanced
- Duration: Short (3-5 min) / Medium (5-10 min) / Long (10-15 min)
- Style Preferences: Colors, pacing, formality
Step 2: Scene Breakdown (@scene-designer)
Create the video structure:
# Video: [Title]
**Total Duration**: ~X minutes
**Scene Count**: Y scenes
## Scene List
| # | Scene Name | Duration | Concept | Camera |
|---|------------|----------|---------|--------|
| 1 | TitleScene | 20s | Video title | static |
| 2 | MotivationScene | 60s | Why this matters | static |
| 3 | ... | ... | ... | ... |
## Detailed Scene Plans
### Scene 1: TitleScene (20s)
[Timeline and technical requirements]
### Scene 2: MotivationScene (60s)
[Timeline and technical requirements]
...
Step 3: Shared Configuration
Create a config module used by all scenes:
# video_config.py
from manim import *
# Video Title
VIDEO_TITLE = "Understanding [Topic]"
# Semantic Color Palette (consistent across all scenes)
COLORS = {
"PRIMARY": BLUE, # Main concept (e.g., the function)
"SECONDARY": ORANGE, # Supporting concept (e.g., derivatives)
"POSITIVE": GREEN, # Success, correct answers
"EMPHASIS": PURPLE, # Highlights, key insights
"MUTED": GRAY, # De-emphasized, background
}
# Typography
FONTS = {
"TITLE": 52,
"SECTION": 42,
"BODY": 28,
"SMALL": 24,
"FORMULA": 38,
}
# Timing Constants
TIMING = {
"FAST": 0.5,
"NORMAL": 1.0,
"SLOW": 2.0,
"DRAMATIC": 3.0,
"BRIEF": 0.5,
"STANDARD": 1.0,
"EXTENDED": 2.0,
"COMPLEX": 4.0,
"CRITICAL": 6.0,
}
# Base Scene Class
class VideoScene(Scene):
"""Base class for all scenes in this video"""
def setup(self):
self.tracked = []
def track(self, *mobjects):
for m in mobjects:
self.tracked.append(m)
self.add(m)
return mobjects[0] if len(mobjects) == 1 else mobjects
def cleanup(self, keep=None):
keep = keep or []
to_remove = [m for m in self.tracked if m not in keep]
if to_remove:
self.play(*[FadeOut(m) for m in to_remove])
self.tracked = list(keep)
def section_title(self, text):
"""Standard section title animation"""
title = Text(text, font_size=FONTS["SECTION"])
self.play(Write(title), run_time=TIMING["NORMAL"])
self.wait(TIMING["BRIEF"])
self.play(title.animate.to_edge(UP, buff=0.5))
return title
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.
- yesterday First seen · 252 lines · 16 tokens per session scan A 0f1f871431ab
create-video is a command published in the GitHub repository choxos/MathVizAgent (1 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 1,588 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-31.
Other commands, from other repositories
d3mo-generator
Professional video production system using Remotion and advanced animation techniques for demos, tutorials, and marketing content by ae.ltd.
recburnclick
Screen + system-audio recording with a live "CLICKS: n" counter burned into the video. Counts every mouse-down from the moment recording starts. No Accessibility permission, no event tap.
screen-audio-record
Record the screen AND audio straight off the system audio engine — no microphone, no loopback driver (BlackHole/Loopback), no virtual cable. Scope the audio to a single app (e.g. Renoise) or grab all system audio. Apple-native ScreenCaptureKit. Ctrl-C stops and finalizes the .mov.
notebooklm
Google NotebookLM programmatic access — create notebooks, manage sources (URLs, PDFs, YouTube, Drive), generate audio/video/slides/quizzes, and chat with documents. Use when building a research notebook, generating a podcast from docs, or querying a source collection. Triggers on notebooklm, podcast from docs…
notebook-studio
Generate a studio artifact (audio, video, slides, quiz, etc.).
video-new
Create a new Remotion video project with TTS and animations.