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 skills/leventilo/mobius/primitive-generatornpx skills add leventilo/mobius --skill primitive-generatorgit clone --depth 1 https://github.com/leventilo/mobiusWhat 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.00066 | $0.05629 |
| Opus 5 | $0.00033 | $0.02815 |
| Sonnet 5 | $0.00013 | $0.01126 |
| Haiku 4.5 | $0.00007 | $0.00563 |
Grade A, and why
primitive-generator scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Rejected: `os`, `subprocess`, `socket`, `requests`, `urllib`, `http`, `ftp`, `pickle`, `eval`, `exec`, `__import__`. Any rejected import is a hard validator fail. How it starts
The opening of the file, as written. The whole thing — 388 lines — stays where its author put it; the contents beside it link to each section on GitHub.
primitive-generator
1. Purpose and scope
This skill produces the executable artifact of every Mobius simulation: the Python code that fills primitives[i].python_code in the SimSpec. The SimSpec arrives from simspec-author with the physics, simulation, and primitives subtrees populated, but with python_code fields empty. This skill writes that code, primitive by primitive, then hands the SimSpec back to the orchestrator. science-integrity runs immediately afterward and gates execution by Managed Agents.
Three things this skill does NOT do. It does not invent physics — physics-interpreter already chose the regime, the equations, and the approximations. It does not validate units, CFL, or conservation — those are five separate scripts shipped by science-integrity. It does not orchestrate primitive ordering or DAG resolution — that is the orchestrator's job using primitives[i].depends_on.
The skill is stateless across primitives: each primitive is generated independently, and depends_on ordering is enforced by the caller, not by this skill. This decouples primitive generation from graph topology and makes the skill reusable by any future Mobius DAG variant.
2. Input
A full SimSpec object on disk as simspec.json, or passed inline by the orchestrator. Required state:
paper.*— only used for cache-key computation (abstractHash).physics.regime,physics.approximations,physics.governing_equations[*].domain_hints— drive pattern matching.primitives[*]— every entry hasid,type,name,parameters,depends_on,viz_hint, butpython_codeis empty.simulation.rng_seed— injected into every stochastic primitive.simulation.solver_hints.scheme— used to disambiguate when multiple patterns could match.
If python_code is already non-empty for a primitive, the skill skips it (idempotent re-runs are safe).
3. Output
The same SimSpec object with python_code filled for every primitive. The skill also appends entries to integrity.checks[] of type ambiguity:
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- patterns/_runtime/__init__.py 2.4 KB runs code
- patterns/.gitkeep 0 B
- patterns/em_fdtd_2d.json 4.2 KB
- patterns/fluid_stokes_sphere.json 3.1 KB
- patterns/mech_double_pendulum.json 2.9 KB
- patterns/mech_rk4_oscillator.json 2.1 KB
- patterns/qm_split_step_1d.json 3.0 KB
- patterns/statmech_ising_2d.json 2.3 KB
- patterns/thermo_heat_2d.json 3.3 KB
- patterns/wave_double_slit.json 2.1 KB
- patterns/wave_gaussian_source.json 1.7 KB
- patterns/wave_screen_intensity.json 1.5 KB
- patterns/wave_thin_lens.json 1.7 KB
- scripts/validate_primitive.py 14 KB runs code
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.
- 2d ago First seen · 388 lines · 66 tokens per session scan A 80b602d3991e
primitive-generator is a skill published in the GitHub repository leventilo/mobius (9 stars, last pushed 4mo ago), licensed MIT. It adds 66 tokens to every session and 5,629 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.