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 skills add dyCuong03/unity-agent-team --skill codebase-understandinggit 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/skills/dycuong03/unity-agent-team/codebase-understanding)<a href="https://agentmods.dev/skills/dycuong03/unity-agent-team/codebase-understanding"><img src="https://agentmods.dev/badge/skills/dycuong03/unity-agent-team/codebase-understanding/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/skills/dycuong03/unity-agent-team/codebase-understanding"><img src="https://agentmods.dev/badge/skills/dycuong03/unity-agent-team/codebase-understanding.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.00054 | $0.00652 |
| Opus 5.5 | $0.00022 | $0.00261 |
| Sonnet 5.5 | $0.00011 | $0.00130 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
codebase-understanding 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
Codebase Understanding — CRG-First
Core Rule
Query code-review-graph before reading any file. Never guess from filenames. Never grep blindly.
When to Use Each Agent
| Task | Agent | First CRG Call |
|---|---|---|
| Understand system architecture | architecture-agent |
get_architecture_overview |
| Read an unfamiliar feature | codebase-reader |
get_minimal_context |
| Investigate a bug | bug-investigation |
trace_execution_flow |
| Plan a refactor | refactor-agent |
get_impact_radius |
| Implement a new feature | feature-dev-agent |
find similar feature |
CRG Tool Reference
| Tool | Use Case |
|---|---|
get_architecture_overview |
Full system map before any analysis |
trace_execution_flow |
Follow what runs in what order |
get_minimal_context |
Orient around an unfamiliar symbol |
find_entry_points |
Where does this feature start? |
list_related_symbols |
What symbols participate in this feature? |
trace_callers_callees |
Who calls this? What does it call? |
get_impact_radius |
What breaks if I change this? |
trace_dependencies |
What does this depend on? |
identify_shared_symbols |
What is used by many callers? |
identify_extension_points |
Where does new code attach? |
File Read Limit
Maximum 8 files per investigation, each justified by graph evidence.
Fallback (no CRG)
State "Running without CRG evidence" once. Use targeted Grep on known symbols. Read only files directly implicated. State your reasoning for each file opened.
Output Template
## Summary
<one paragraph>
## Execution Flow
<numbered steps>
## Relevant Systems
<list with ownership>
## Root Cause / Behavior
<precise statement>
## Impact Radius
<what would change if this is modified>
## Recommended Next Step
<single concrete action>
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 · 80 lines · 54 tokens per session scan A 7f32a8424d0a
codebase-understanding is a skill published in the GitHub repository dyCuong03/unity-agent-team (7 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 652 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 skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…