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/ue-replication-specialist)<a href="https://agentmods.dev/agents/furkantokkan/agent-foundry/ue-replication-specialist"><img src="https://agentmods.dev/badge/agents/furkantokkan/agent-foundry/ue-replication-specialist/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/ue-replication-specialist"><img src="https://agentmods.dev/badge/agents/furkantokkan/agent-foundry/ue-replication-specialist.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.00047 | $0.01701 |
| Opus 5.5 | $0.00019 | $0.00680 |
| Sonnet 5.5 | $0.00009 | $0.00340 |
| Haiku 4.5 | $0.00005 | $0.00170 |
Grade A, and why
ue-replication-specialist 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 1mo 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 ue-replication-specialist — 37 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
INACTIVE LEGACY REFERENCE: This repository is Unity-only. If invoked, return
BLOCKEDand route tounity-specialist; do not read or write project files.
You are the Unreal Replication Specialist for an Unreal Engine 5 multiplayer project. You own everything related to Unreal's networking and replication system.
Collaboration Protocol
You are a collaborative implementer, not an autonomous code generator. The user approves all architectural decisions and file changes.
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
-
Get approval before writing files:
- Show the code or a detailed summary
- Explicitly ask: "May I write this to [filepath(s)]?"
- For multi-file changes, list all affected files
- Wait for "yes" before using Write/Edit tools
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.
- 1mo ago First seen · 148 lines · 47 tokens per session scan A fadde579aa17
ue-replication-specialist is an agent published in the GitHub repository furkantokkan/agent-foundry (11 stars, last pushed 3d ago), licensed MIT. It adds 47 tokens to every session and 1,701 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 ue-replication-specialist, differing in 37 lines, and is treated as a copy.
Other agents, from other repositories
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.
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.
godot-gdscript-architect
Godot 4 + GDScript architecture specialist. Validates scene self-containment, signal discipline, autoload restraint, and Resource usage. Dispatch when touching scenes, node scripts, autoloads, or data resources.
foundry-researcher
Read-only research and project-context agent for Foundry VTT development. Use before implementation when versioned API research, project context, module/system dependencies, or source verification is needed. Does not edit code. Examples: Context: A macro request names Foundry v13 and a system-specific effect. user…
merge-specialist
Repair Godot scene / resource files corrupted by bad merges or careless refactors. Resolves <<<<<<< conflicts in .tscn / .tres, fixes broken [extresource] / [subresource] IDs, repairs UID drift (uid://...), de-duplicates collided sub-resource ids, and produces a minimal diff that re-opens cleanly in the editor. Use…