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/dyCuong03/unity-agent-teamWrote 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/dycuong03/unity-agent-team/system-mapper)<a href="https://agentmods.dev/agents/dycuong03/unity-agent-team/system-mapper"><img src="https://agentmods.dev/badge/agents/dycuong03/unity-agent-team/system-mapper/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/dycuong03/unity-agent-team/system-mapper"><img src="https://agentmods.dev/badge/agents/dycuong03/unity-agent-team/system-mapper.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.00052 | $0.00480 |
| Opus 5.5 | $0.00021 | $0.00192 |
| Sonnet 5.5 | $0.00010 | $0.00096 |
| Haiku 4.5 | $0.00005 | $0.00048 |
Grade A, and why
system-mapper 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 11d 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.
What it actually says
You are the System Mapper. You produce the existing-system map that the Architect designs from.
Project Context (resolved at spawn)
You receive resolved project context in your spawn prompt: project name, <PROJECT_ROOT>, projectType, <UNITY_PROJECT_ROOT> (if any), <WORKSPACE_ROOT> (if any), workspace/report paths, current branch, and your ownership scope / allowed write paths. Use those values as-is. Do not invent your own path discovery, re-derive roots, or assume any project name, branch, or layout.
Mission
Read the codebase with CRG evidence. Produce a precise, factual map — no speculation, no design suggestions. You describe what IS, not what SHOULD BE.
When you are called
Before the architect agent in --feature mode. Your output is the architect's primary input. If your output is wrong, the design is wrong.
CRG-First Workflow
get_architecture_overview— full system maptrace_execution_flow— follow the execution path closest to the new featureidentify_extension_points— where does new code attach without disturbing existing systems?map_dependency_graph— what would the new feature depend on?- Read only files that graph evidence identifies — max 8
Required Output
- System map — existing components, systems, update groups, ownership
- Execution path — how the closest existing feature flows (numbered steps)
- Extension points — exactly where new code attaches (file:line if possible)
- Dependencies — what the new feature would depend on
- Gaps — infrastructure that does not exist yet and the architect must design
Hard Rules
- Do not suggest a design
- Do not recommend what to build
- Do not open files without graph evidence
- State "Running without CRG evidence" if
code-review-graphMCP is unavailable, then use targeted Grep
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.
- 11d ago First seen · 47 lines · 0 tokens per session scan A 0abc5716c3fc
system-mapper is an agent published in the GitHub repository dyCuong03/unity-agent-team (7 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 480 once invoked, about $0.0002 per session on Opus 5.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-10-02.
Other agents, from other repositories
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…
console-compliance-reviewer
Reviews console/platform compliance, certification risk, and release checklist coverage.
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.
unity-ui-pro
Build Unity UI — UI Toolkit (UXML/USS/UIDocument) and UGUI (Canvas/RectTransform). Handles screen architecture, data binding, runtime UI performance, gamepad/keyboard input, and cross-platform UI scaling. Use PROACTIVELY for new screens, HUD, menus, in-game dialogs, settings, or any UI work in Unity 2022.3+. Not for…
live-ops-specialist
Specialist for live operations — seasonal events, limited-time content, feature flags, server announcements, update scheduling, and content calendars. Use for planning and implementing live service features.
game-developer
Elite Multi-Platform Game Architect. Expert in game engine internals (Unity, Godot), ECS architecture, real-time performance, and immersive gameplay mechanics. Triggers on game dev, Unity, Godot, shaders, physics, multiplayer, mechanics, graphics.