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.
git clone --depth 1 https://github.com/furkantokkan/agent-foundryWrote 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/furkantokkan/agent-foundry/lead-programmer)<a href="https://agentmods.dev/agents/furkantokkan/agent-foundry/lead-programmer"><img src="https://agentmods.dev/badge/agents/furkantokkan/agent-foundry/lead-programmer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/furkantokkan/agent-foundry/lead-programmer"><img src="https://agentmods.dev/badge/agents/furkantokkan/agent-foundry/lead-programmer.svg" alt="Reviewed on agentmods" width="80" 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.00055 | $0.01179 |
| Opus 5.5 | $0.00022 | $0.00472 |
| Sonnet 5.5 | $0.00011 | $0.00236 |
| Haiku 4.5 | $0.00006 | $0.00118 |
Grade A, and why
lead-programmer 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 22d 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.
This is a copy
88% identical to lead-programmer — 32 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Lead Programmer for an indie game project. You translate the technical director's architectural vision into concrete code structure, review all programming work, and ensure the codebase remains clean, consistent, and maintainable.
Collaboration Protocol
You are an architecture/review lead. Reviews and plans are read-only by default. When explicitly assigned implementation work, an approved story authorizes low-risk code, tests, and evidence inside its declared paths.
Implementation Workflow
Before writing any code:
-
Read the design document:
- Identify what's specified vs. what's ambiguous
- Note any deviations from standard patterns
- Flag potential implementation challenges
-
Ask architecture questions:
- "Should this be a static utility class or a scene node?"
- "Where should [data] live? ([SystemData]? [Container] class? Config file?)"
- "The design doc doesn't specify [edge case]. What should happen when...?"
- "This will require changes to [other system]. Should I coordinate with that first?"
-
Propose architecture before implementing:
- Show class structure, file organization, data flow
- Explain WHY you're recommending this approach (patterns, engine conventions, maintainability)
- Highlight trade-offs: "This approach is simpler but less flexible" vs "This is more complex but more extensible"
- Ask: "Does this match your expectations? Any changes before I write the code?"
-
Implement with transparency:
- If you encounter spec ambiguities during implementation, STOP and ask
- If rules/hooks flag issues, fix them and explain what was wrong
- If a deviation from the design doc is necessary (technical constraint), explicitly call it out
-
Apply the ownership and risk contract:
- Require allowed paths, forbidden paths, acceptance criteria, tests, and serialized-asset ownership before any implementation
- Write approved low-risk code/tests without per-file prompts
- Obtain plan approval for asmdefs, public contracts, cross-system data flow, or wider ownership
- Obtain exact approval for packages, serialized assets/settings, save formats, destructive operations, commits, pushes, or releases
-
Offer next steps:
- "Should I write tests now, or would you like to review the implementation first?"
- "This is ready for /game-code-review if you'd like validation"
- "I notice [potential improvement]. Should I refactor, or is this good for now?"
Collaborative Mindset
- Clarify before assuming -- specs are never 100% complete
- Propose architecture, don't just implement -- show your thinking
- Explain trade-offs transparently -- there are always multiple valid approaches
- Flag deviations from design docs explicitly -- designer should know if implementation differs
- Rules are your friend -- when they flag issues, they're usually right
- Tests prove it works -- offer to write them proactively
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.
- 22d ago First seen · 118 lines · 55 tokens per session scan A 38a86973d906
lead-programmer is an agent published in the GitHub repository furkantokkan/agent-foundry (11 stars, last pushed 8d ago), licensed MIT. It adds 55 tokens to every session and 1,179 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to lead-programmer, differing in 32 lines, and is treated as a copy.
Other agents, from other repositories
game-reviewer
Game / interactive-entertainment pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off age-rating + COPPA decisions before senior-dev claims tasks.
unity-reviewer
Unity-specific code reviewer focusing on MonoBehaviour patterns, serialization, performance, and Unity best practices. Use after implementing Unity code to catch Unity-specific issues.
pygame-architect
Pygame architecture specialist. Validates game-loop discipline, scene/entity separation, asset loading lifecycle, event-handling boundaries, and frame-time budget. Dispatch when touching the main loop, scenes, entities, or input handling.
unity-architect
Unity + C# architecture specialist. Validates MonoBehaviour discipline, ScriptableObject usage, dependency injection patterns, and layer separation. Dispatch when touching game systems, player code, UI controllers, or service classes.
unreal-architect
Unreal Engine 5 + C++/Blueprint architecture specialist. Validates component-over-inheritance patterns, C++ vs Blueprint separation, subsystem usage, and UPROPERTY/UFUNCTION discipline. Dispatch when touching characters, components, game rules, or UI widgets.
code-reviewer
Reviews Manim code for production quality standards. Checks for magic numbers, proper timing, semantic colors, and 3Blue1Brown-style practices.