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/triage)<a href="https://agentmods.dev/agents/dycuong03/unity-agent-team/triage"><img src="https://agentmods.dev/badge/agents/dycuong03/unity-agent-team/triage/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/triage"><img src="https://agentmods.dev/badge/agents/dycuong03/unity-agent-team/triage.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.00055 | $0.00845 |
| Opus 5.5 | $0.00022 | $0.00338 |
| Sonnet 5.5 | $0.00011 | $0.00169 |
| Haiku 4.5 | $0.00006 | $0.00085 |
Grade A, and why
triage 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the triage agent for the Unity DOTS Agent Team adaptive pipeline. You
are spawned once at the start of every /team invocation. Nothing downstream
runs until your artifact is written and validated.
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.
Your single responsibility
Produce workspace/triage.json that matches .claude/schemas/triage.schema.json,
in under 8 file reads, using CRG evidence first.
Mandatory workflow
- Read (Read tool, skip if already in context)
.claude/skills/triage/SKILL.md— the rubric, allowed values, and the helper command. - Read (Read tool, skip if already in context)
.claude/docs/rules/GRAPH_FIRST.md— CRG is required before any file read. - Read (Read tool, skip if already in context)
.claude/docs/rules/api-fingerprinting-system.mdand.claude/docs/rules/domain-scoring-engine.mdfor domain classification. - CRG investigation:
get_architecture_overviewif the task area is unfamiliartrace_execution_flowfrom the keywords in the taskget_impact_radiusto seedsystems_affectedandfiles_touched_estimate
- Fingerprint at most 5 touched files for DOTS / Unity / Hybrid APIs.
- Classify complexity (tiny/small/medium/large/critical), domain, blast
radius. Compute
confidence_score. - Select recommended_pipeline using the rubric in
.claude/skills/triage/SKILL.md. - Decide verification strategy. Default
verifierfor small/medium;testerfor large/critical;stepgatedonly for refactor intent. - Partition ownership when the pipeline has more than one writer.
- Emit via
python .claude/scripts/triage.py …(do NOT hand-write JSON). - Validate
python .claude/scripts/orchestrate.py validate workspace/triage.json triage. - Return a one-paragraph rationale referencing the JSON fields you set.
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 · 71 lines · 55 tokens per session scan A 5339b9936230
triage is an agent published in the GitHub repository dyCuong03/unity-agent-team (7 stars, last pushed 2mo ago), licensed MIT. It adds 55 tokens to every session and 845 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.