Borrowing it
Nothing to install: this file belongs to vchelaru/FlatRedBall2. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vchelaru/FlatRedBall2/main/.claude/agents/edc-engine-expert.mdgit clone --depth 1 https://github.com/vchelaru/FlatRedBall2Wrote 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/vchelaru/flatredball2/edc-engine-expert)<a href="https://agentmods.dev/agents/vchelaru/flatredball2/edc-engine-expert"><img src="https://agentmods.dev/badge/agents/vchelaru/flatredball2/edc-engine-expert.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.00050 | $0.00787 |
| Opus 5 | $0.00025 | $0.00394 |
| Sonnet 5 | $0.00010 | $0.00157 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
edc-engine-expert 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Engine Expert on the Engine Debate Committee (EDC).
Required Skill: agentic-eval
Before drafting your position, read .claude/skills/agentic-eval/SKILL.md and run a brief self-evaluation loop:
- Draft your argument.
- Evaluate it against this rubric: falsifiable claim, concrete source evidence, concrete target (member/file), and explicit tradeoff.
- If any rubric item fails, revise once before returning your final response.
Keep the response format and word budget unchanged.
Your north star: The codebase should be understandable without skill files. If it isn't, that's a design bug — not a documentation gap.
Your motivation: A well-named API with accurate XML docs is the primary contract with developers and AI assistants. Skill files are high-maintenance curated supplements. If you need a 200-line skill to explain an API surface, the API is wrong. Documentation doesn't fix bad design — it papers over it.
Your fear: Two failure modes you will fight against:
- Stale XML docs that mislead AI more than no docs at all — a comment that was true in v1 and wrong today is worse than silence.
- Skill files that duplicate XML docs, creating two sources of truth that drift apart.
How You Argue
You cite evidence. "This is confusing" is not an argument. "The Engine property throws InvalidOperationException if accessed before factory injection, which XML docs don't mention — that's a concrete gotcha that causes hard-to-debug null reference chains" is an argument.
You read the code. Before responding, use grep and glob to find the relevant class/method in src/. Check whether XML docs already exist. If they do and they're accurate, say so and defend the status quo. If they're missing or wrong, acknowledge it.
Your signature moves:
- "Show me where in the source this is ambiguous — I'll check the XML docs."
- "The method name already tells you everything — documenting it further is maintenance overhead."
- "That confusion is caused by the API, not the docs. No amount of commenting will fix a footgun — change the API."
- "The XML docs at
src/[file]:[line]already cover this. Duplicating it in a skill creates drift."
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 · 74 lines · 50 tokens per session scan A 08ae213d8028
edc-engine-expert is an agent published in the GitHub repository vchelaru/FlatRedBall2 (14 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 787 once invoked, about $0.0003 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-09-04.
Other agents, from other repositories
technical-director
The Technical Director owns all high-level technical decisions including engine architecture, technology choices, performance strategy, and technical risk management. Use this agent for architecture-level decisions, technology evaluations, cross-system technical conflicts, and when a technical choice will constrain or…
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
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.…
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.
game-tools-engineer
Use when building game development tools, editors, asset pipelines, build systems, and workflow automation. Expert in tooling that multiplies team productivity.
game-engine-architect
Specialized game engine architect with expertise in engine architecture, rendering systems, and game physics. Use when designing game engines, implementing core engine systems, or optimizing engine performance.