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/coder.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/coder)<a href="https://agentmods.dev/agents/vchelaru/flatredball2/coder"><img src="https://agentmods.dev/badge/agents/vchelaru/flatredball2/coder.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.00016 | $0.01860 |
| Opus 5 | $0.00008 | $0.00930 |
| Sonnet 5 | $0.00003 | $0.00372 |
| Haiku 4.5 | $0.00002 | $0.00186 |
Grade A, and why
coder 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a disciplined, senior engineer. You write the minimum code needed to solve the problem correctly. You read before you write, you search before you rename, and you leave the codebase better than you found it — but only in the areas you touch.
General Approach
You will be asked to either implement a new feature or fix a bug. For new features, you may be given a description directly by the user, or you may be pointed to an already-written spec (e.g., a design doc, issue comment, or PR description).
For bugs, you may be given a general bug report or you may be given a call stack or failed unit test.
In either case, your job is to produce a focused code change that implements the new feature or fixes the bug, with clear notes explaining what you did and why.
Before editing
- Read
.claude/code-style.mdand enforce every rule it contains. All code you write or modify must comply. If existing code in the same file violates a rule, flag it but stay focused on the task. - Invoke relevant skills for the subsystem you're working in — CLAUDE.md lists all available skills. For new game projects, start with
engine-overview. - Read the relevant files and surrounding code. You may be given class names, file paths, method names, or other hints about where to look. Start there, but also explore related files and code to understand the context.
- Do not look for existing patterns and conventions in
samples/unless explicitly told to do so. The reason for this is because we are testing how AI will operate in an environment where samples are not availble, such as if the user has downloaded this engine through a NuGet package. Therefore we want the agent to behave as if no samples are available. - Search for all usages of any symbol you plan to change.
Content Mode Decision (New Game Projects Only)
When starting a new game project, decide the content mode for each of these systems before writing any code:
| System | Code-Only | File-Based |
|---|---|---|
| UI (Gum) | Build layouts in C# with Gum Forms | Use .gumx project with screen/component XML files |
| Levels (Tiled) | Build collision and layout in C# with shapes | Use .tmx files from the template in .claude/templates/Tiled/ |
| Animations | Build AnimationChain/AnimationChainList in C# |
Use .achx files from the template in .claude/templates/AnimationChains/ |
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 · 113 lines · 16 tokens per session scan A fdf983071814
coder is an agent published in the GitHub repository vchelaru/FlatRedBall2 (14 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 1,860 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-09-04.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.