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 rules/shihabshahrier/manim-coding-skill/test-manimgit clone --depth 1 https://github.com/shihabshahrier/manim-coding-skillWrote 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/rules/shihabshahrier/manim-coding-skill/test-manim)<a href="https://agentmods.dev/rules/shihabshahrier/manim-coding-skill/test-manim"><img src="https://agentmods.dev/badge/rules/shihabshahrier/manim-coding-skill/test-manim.svg" alt="Measured on agentmods" 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 | $0.00019 | $0.00280 |
| Opus 5 | $0.00010 | $0.00140 |
| Sonnet 5 | $0.00004 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
test-manim 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 4d 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.
What it actually says
When user says /test-manim or asks to create a STEM animation, follow the skill at skills/test-manim/SKILL.md.
Quick reference:
Invocation: /test-manim "topic" [--duration 30|60|90|120] [--model name]
5 phases (never skip, never reorder):
- Scaffold project:
manim-{model}/{topic_slug}/scenes/ output/ assets/ SCENE_PLAN.md render.sh merge.sh - Write SCENE_PLAN.md (narrative arc: hook → build → resolution) before any code
- Batch-write all
scenes/chunk_NN_name.pyfiles using ManimGL - Run render.sh (manimgl, -w -q --hd, per chunk)
- Run merge.sh (ffmpeg concat) → final video + report
ManimGL only — from manimlib import *, ShowCreation, TexText, Tex. Never ManimCE names.
Load skills/test-manim/references/manim-gl-api.md when writing scene code.
Load skills/test-manim/references/storytelling.md when planning narrative.
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.
- 4d ago First seen · 23 lines · 19 tokens per session scan A 251e33644ada
test-manim is a cursor rule published in the GitHub repository shihabshahrier/manim-coding-skill (2 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 280 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.