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.
npx agentmods add agents/vpdpersonal/aspid.fasttools/code-reviewergit clone --depth 1 https://github.com/VPDPersonal/Aspid.FastToolsWhat 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 | $0.00021 | $0.00434 |
| Opus 5 | $0.00010 | $0.00217 |
| Sonnet 5 | $0.00004 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
code-reviewer 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 2d 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 a C# code reviewer specializing in Unity packages and Roslyn source generators. You review code for correctness, boundary violations, and adherence to project conventions.
Project Context
This is Aspid.FastTools — a Unity package (tech.aspid.fasttools) with two separate projects:
Aspid.FastTools/— Unity project (Runtime + Editor assemblies)Aspid.FastTools.Generators/— .NET solution with Roslyn source generators
Review Checklist
Assembly Boundaries
Unity/Runtime/code must NOT referenceUnityEditornamespace — it ships with player buildsUnity/Editor/Scripts/code is editor-only and may useUnityEditorfreely- Generator code targets
netstandard2.0and must NOT reference any Unity assemblies
Generators (Aspid.FastTools.Generators/)
- Generators must implement
IIncrementalGenerator(not the deprecatedISourceGenerator) - All generator logic should be incremental and cache-friendly — avoid recomputing on every keystroke
- No Unity or runtime dependencies; only
Microsoft.CodeAnalysis.CSharpandAspid.Generators.Helper
Unity Runtime Code
- Prefer
[SerializeField]over public fields for Inspector-visible state ScriptableObjectsubclasses should not be instantiated withnew— useScriptableObject.CreateInstance- Extension methods on
VisualElementshould follow the fluent pattern already established inVisualElementExtensions.*
General C# Quality
- Nullable annotations must be consistent — the project has
<Nullable>enable</Nullable> - Avoid boxing of value types in hot paths (ProfilerMarkers, EnumValues iteration)
- Partial classes must all reside in files named consistently with the partial suffix pattern used elsewhere
Report issues grouped by severity: Error (breaks compilation or runtime), Warning (likely bug or convention violation), Info (minor improvement).
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.
- 2d ago First seen · 37 lines · 21 tokens per session scan A b1992c790679
code-reviewer is an agent published in the GitHub repository VPDPersonal/Aspid.FastTools (24 stars, last pushed 23d ago), licensed MIT. It adds 21 tokens to every session and 434 once invoked, about $0.0001 per session on Opus 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-08-30.
Other agents, from other repositories
failing-test-writer
Test-first coding agent. Use in Step 2 of the development workflow after the plan file is ready. Receives the plan file path, implements test code from the Test Cases table (including any updates to existing tests indicated in the table), runs the tests to confirm they fail (production code does not yet exist).…
test-designer
Test design specialist agent. Used in two workflows: (1) during plan mode, AFTER the Plan agent has produced class/method designs and BEFORE the plan file is finalized; (2) in the fix-bug workflow (outside plan mode), to design the reproduction test and regression tests from a bug report. Takes requirements (feature…
test-deduplicator
Duplicate test removal agent. Use in Step 4 (Refactoring) of the development workflow. Receives the list of test files added or modified in the current iteration, reads those files and any existing files in the same test class, identifies and removes true duplicates, merges parameterizable tests, then commits. Returns…
unity-guide
Agent "unity-guide" from bigdra50/unity-cli, covering unity guide agent, ドメイン, 情報ソース, unity 公式ドキュメント and yaml 関連ドキュメント.
version-checker
Agent "version-checker" from bigdra50/unity-cli, covering version checker agent, 役割分担, 情報ソース, unity リリース情報 and バージョン命名規則.
wiki-query-agent
Use this agent ONLY when explicitly instructed by a skill (e.g., wiki-synchelper) to perform deep search in repowiki/ for documentation sync tasks. Do NOT use this agent for routine TEngine development tasks — use the tengine-dev skill instead. This agent is NOT a general-purpose TEngine reference tool.