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/AmaniDawn/DGameWrote 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/commands/amanidawn/dgame/profiling-and-memory)<a href="https://agentmods.dev/commands/amanidawn/dgame/profiling-and-memory"><img src="https://agentmods.dev/badge/commands/amanidawn/dgame/profiling-and-memory/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/commands/amanidawn/dgame/profiling-and-memory"><img src="https://agentmods.dev/badge/commands/amanidawn/dgame/profiling-and-memory.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.00000 | $0.02212 |
| Opus 5.5 | $0.00000 | $0.00885 |
| Sonnet 5.5 | $0.00000 | $0.00442 |
| Haiku 4.5 | $0.00000 | $0.00221 |
Grade A, and why
profiling-and-memory 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 yesterday.
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.
This is a copy
100% identical to profiling-and-memory — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Profiling & memory capture commands
Record a Profiler capture (.data) or take a memory snapshot (.snap) from a running Editor or a
connected development Player. Both follow the diagnostics run_audit shape: the start command returns
immediately, and you poll a *_status command until it reports completed, then read the path it
gives you.
Both capture from whatever the Editor's Profiler is connected to: the same connection the Profiler
window's target dropdown sets. Choose it with diagnostics profiler_connect, or leave it where it is.
unity command diagnostics profiler_targets
unity command diagnostics profiler_connect --target editor
unity command diagnostics profiler_record --frames 300
unity command diagnostics profiler_record_status
Targets
diagnostics profiler_targets
List what the Editor's Profiler can connect to: this Editor plus any connected development Players.
current marks what diagnostics profiler_record and diagnostics memory_snapshot capture from.
No parameters.
Returns: object — { status, current, targets: [{ guid, name, isEditor, connectable, current, deepProfilingSupported }] }.
Notes: isEditor means this Editor process, guid -1. A connection to another Editor is an
ordinary remote target. deepProfilingSupported is false for a Player built without Deep Profiling
Support. A Player attached through Autoconnect Profiler does not appear in Unity's own target list, so
the current connection is always listed even when Unity omits it.
diagnostics profiler_connect
Point the Editor's Profiler connection at a target, as choosing it in the Profiler window does. The connection stays there afterwards.
| Parameter | Required | Default | Description |
|---|---|---|---|
target |
yes | – |
editor for this Editor, or a guid or name from diagnostics profiler_targets. A name may be a unique part of one. |
Returns: object — { status: "ok", target, guid, switched, message? }, or { status: "error" | "busy", message }.
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.
- yesterday First seen · 164 lines · 0 tokens per session scan A cf347d73b04a
profiling-and-memory is a command published in the GitHub repository AmaniDawn/DGame (177 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,212 tokens. A static security scan graded it A with 0 findings. It is 100% identical to profiling-and-memory, differing in 0 lines, and is treated as a copy.
profiling-and-memory compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| profiling-and-memoryAmaniDawn/DGame | Command | 177 | 2d ago | MIT | A | 0 | Claude Code |
| qa-changesOpenHands/extensions | Command | 178 | today | MIT | A | 63 | Claude Code |
| react-nativegetsentry/toolkit | Command | 958 | today | none | A | 0 | Claude Code |
| auditar-cascadingluanpdd/kit-mcp | Command | 5 | 5d ago | MIT | A | 54 | Claude Code |
| http-serviceMadAppGang/magus | Command | 14 | today | MIT | A | 27 | Claude Code |
| doctordoncheli/don-cheli-sdd | Command | 59 | 2mo ago | Apache-2.0 | A | 76 | Claude Code |
| doctorfatihkan/badi | Command | 7 | 1mo ago | MIT | A | 0 | Claude Code |