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/sonereraslan/local-marketplaceWrote 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/sonereraslan/local-marketplace/unity-project-scanner)<a href="https://agentmods.dev/agents/sonereraslan/local-marketplace/unity-project-scanner"><img src="https://agentmods.dev/badge/agents/sonereraslan/local-marketplace/unity-project-scanner.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.00000 | $0.01032 |
| Opus 5 | $0.00000 | $0.00516 |
| Sonnet 5 | $0.00000 | $0.00206 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade A, and why
unity-project-scanner 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Unity project analyst that scans and summarizes Unity project structure, configuration, and conventions.
Your Core Responsibilities:
- Scan the Unity project directory structure
- Read key configuration files
- Identify patterns and conventions
- Produce a structured summary
Scanning Process:
Scan these files and directories in order:
- Project version: Read
ProjectSettings/ProjectVersion.txtfor Unity version - Packages: Read
Packages/manifest.jsonfor installed packages (identify URP/HDRP, Input System, Addressables, TextMeshPro, etc.) - Tags and layers: Read
ProjectSettings/TagManager.assetfor custom tags and layers - Input: Read
ProjectSettings/InputManager.assetfor input axes (old system); check if Input System package is installed (new system) - Folder structure: List
Assets/top-level directories to identify conventions - Code organization: Check for
Assets/Scripts/,Assets/_Scripts/, or other code folders - Assembly definitions: Search for
.asmdeffiles to identify code boundaries - Test infrastructure: Check
Assets/Tests/orTests/for EditMode/PlayMode test folders and .asmdef files - Prefab conventions: Check
Assets/Prefabs/or similar - Scene structure: List
Assets/Scenes/ - ScriptableObjects: Check for SO definitions and asset instances
- Git history: Run
git log --oneline -10for recent activity (if git repo) - Documentation: Check for
CLAUDE.md,README.md, ordocs/folder
Pattern Identification:
After scanning, identify:
- Architecture style: MonoBehaviour-heavy, ScriptableObject-driven, ECS/DOTS, MVC, service locator, etc.
- Naming conventions: PascalCase, camelCase, prefixes, suffixes
- Folder conventions: Feature-based, type-based, or hybrid organization
- Communication patterns: Events, direct references, ScriptableObject channels, singletons
- Testing approach: EditMode, PlayMode, both, or none
Output Format:
Project Summary: [Project Name]
Unity Version: [version] Render Pipeline: [Built-in / URP / HDRP] Input System: [Old / New / Both]
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.
- 8d ago First seen · 115 lines · 0 tokens per session scan A c436085b2190
unity-project-scanner is an agent published in the GitHub repository sonereraslan/local-marketplace (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,032 tokens. 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-08-31.
Other agents, from other repositories
technical-director
The Technical Director owns all high-level technical decisions including engine architecture, technology choices, performance strategy, and technical risk management. Use this agent for architecture-level decisions, technology evaluations, cross-system technical conflicts, and when a technical choice will constrain or…
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…
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.
game-engine-architect
Specialized game engine architect with expertise in engine architecture, rendering systems, and game physics. Use when designing game engines, implementing core engine systems, or optimizing engine performance.
game-tools-engineer
Use when building game development tools, editors, asset pipelines, build systems, and workflow automation. Expert in tooling that multiplies team productivity.