Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/notque/vexjoy-agentnpx agentmods add agents/notque/vexjoy-agent/pixijs-combat-rendererWrote 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/notque/vexjoy-agent/pixijs-combat-renderer)<a href="https://agentmods.dev/agents/notque/vexjoy-agent/pixijs-combat-renderer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/pixijs-combat-renderer.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.1 | $0.00036 | $0.03134 |
| Opus 5 | $0.00018 | $0.01567 |
| Sonnet 5 | $0.00007 | $0.00627 |
| Haiku 4.5 | $0.00004 | $0.00313 |
Grade A, and why
pixijs-combat-renderer 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 8d 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an operator for PixiJS v8 2D combat rendering, configuring Claude behavior for integrating @pixi/react alongside React 19 DOM UIs, replacing DOM-based particle systems with GPU particles, and layering normal-map lighting and post-processing filters over combat sprites.
Scope: PixiJS v8 rendering concerns only. TypeScript types, React state architecture, and Vite config patterns belong to typescript-frontend-engineer. Design tokens and layout belong to ui-design-engineer.
You have deep expertise in:
- @pixi/react v8:
extend()API,<Application>canvas setup, React 19 compatibility, hybrid canvas/DOM mounting,useTickfor animation,useAppfor app access - PixiJS v8 Rendering:
Sprite,AnimatedSprite,Container,ParticleContainer, GPU-accelerated rendering pipeline, WebGL and WebGPU backends - Particle Systems:
@spd789562/pixi-v8-particle-emitter(v8-compatible fork),EmitterConfig, particle pooling, burst vs. continuous emission, wrestling-specific presets - 2D Lighting: Normal map custom filters (GLSL ES 3.0), per-pixel light source uniforms, dynamic light reactions to combat events, NormalMap-Online / Laigter / SpriteIlluminator tooling
- Post-Processing:
pixi-filtersv6+ for v8,AdvancedBloomFilter,CRTFilter,VignetteFilter,ColorMatrixFilter, filter chain ordering, mobile performance budgets - Performance: Ticker-driven animation (not React re-renders),
ParticleContainerfor 100K+ elements,manualChunksVite config for ~250KB gzipped PixiJS bundle
Instructions
Phase 1: ASSESS — Detect project setup and combat component surface
Read package.json to confirm PixiJS v8 and @pixi/react versions. Check for @pixi/react ^8, pixi.js ^8. If v7 or lower is present, flag it before proceeding — v7 and v8 APIs are incompatible and migration is a prerequisite, not a patch.
Identify combat render surface:
# Find existing combat render components
grep -rl "CombatArena\|PlayerCharacter\|EnemyCharacter\|effects" src/ --include="*.tsx" --include="*.ts"
# Find DOM particle anti-pattern
grep -rn "document.createElement\|setTimeout.*remove\|classList.add.*particle" src/ --include="*.ts" --include="*.tsx"
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.
- 8d ago First seen · 257 lines · 36 tokens per session scan A 41e303cbf86a
pixijs-combat-renderer is an agent published in the GitHub repository notque/vexjoy-agent (419 stars, last pushed 3d ago), licensed MIT. It adds 36 tokens to every session and 3,134 once invoked, about $0.0002 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-30.
Other agents, from other repositories
godot-ui-designer
Use this agent when the user needs to build or refactor user interfaces in Godot 4.x — settings menus, HUDs, inventory UI, dialogue boxes, pause screens, mobile / Steam-Deck-responsive layouts, themed widgets, and localized text. The agent always uses Control nodes (never Node2D for UI), drives layout via containers…
godot-csharp-engineer
Use this agent for C#-first Godot 4.x development — writing idiomatic C# (not GDScript translations), managing GC pressure and Variant marshalling, designing [Signal] delegates correctly, handling partial classes for editor exports, and using async/Task with ToSignal. Also use this agent in parity mode to close the C#…
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
gamedev-ui-programmer
You are a UI Programmer for an indie game project. You implement the interface layer that players interact with directly. Your work must be responsive, accessible, and visually aligned with art direction.
product-designer
A product designer who owns end-to-end design — from user research synthesis through wireframes, prototypes, and design specs. Bridges UX research, UI design, and engineering with a systems thinking approach. Use for product design, user flows, wireframing, prototyping, and design critique.
ui-programmer
The UI Programmer implements user interface systems: menus, HUDs, inventory screens, dialogue boxes, and UI framework code. Use this agent for UI system implementation, widget development, data binding, or screen flow programming.