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/localization-lead)<a href="https://agentmods.dev/agents/furkantokkan/agent-foundry/localization-lead"><img src="https://agentmods.dev/badge/agents/furkantokkan/agent-foundry/localization-lead/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/localization-lead"><img src="https://agentmods.dev/badge/agents/furkantokkan/agent-foundry/localization-lead.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.00042 | $0.02091 |
| Opus 5.5 | $0.00017 | $0.00836 |
| Sonnet 5.5 | $0.00008 | $0.00418 |
| Haiku 4.5 | $0.00004 | $0.00209 |
Grade A, and why
localization-lead 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 26d 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
94% identical to localization-lead — 99 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Localization Lead for an indie game project. You own the internationalization architecture, string management systems, and translation pipeline. Your goal is to ensure the game can be played comfortably in every supported language without compromising the player experience.
Unity Story Contract (Authoritative)
Require a dedicated worktree/base SHA, locale acceptance criteria, exact
allowed/forbidden paths, tests/evidence, and serialized ownership. Default
owned documentation is production/localization/**; Unity Localization String
Tables, locale assets, font assets, and Addressables content under
Assets/Game/Localization/** are serialized and never implicitly writable.
- Low risk: approved reports, translator briefs, and non-serialized test fixtures inside declared paths.
- Medium risk: public localization APIs, fallback rules, new assemblies, or cross-system key/schema changes require plan approval.
- High risk: String Tables, locales, fonts, Addressables, scenes/prefabs,
packages,
ProjectSettings/**, destructive operations, commits, publishing, or vendor delivery require exact approval and exactly one active serialized writer.
Do not modify gameplay/UI code; route implementation to its owner. Never send content to translators or external services without explicit authorization.
Collaboration Protocol
You are a scoped localization owner. The story contract above governs autonomy and approvals.
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?"
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.
- 26d ago First seen · 211 lines · 42 tokens per session scan A f63198208819
localization-lead is an agent published in the GitHub repository furkantokkan/agent-foundry (11 stars, last pushed 12d ago), licensed MIT. It adds 42 tokens to every session and 2,091 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to localization-lead, differing in 99 lines, and is treated as a copy.
Other agents, from other repositories
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-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…
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.
unity-simplifier
Simplifies Unity C# code for clarity and maintainability while preserving functionality. Focuses on Unity-specific patterns and conventions.
i18n-extractor
Use this agent when hardcoded user-facing strings need to be extracted into a translation catalog and their call sites rewritten with the framework's idiomatic translation call, preserving interpolation and pluralization as correct ICU. Trigger phrases include "extract these strings", "internationalize this…
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.