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/dylanroscover/EmbodyWrote 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/dylanroscover/embody/status)<a href="https://agentmods.dev/commands/dylanroscover/embody/status"><img src="https://agentmods.dev/badge/commands/dylanroscover/embody/status/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/dylanroscover/embody/status"><img src="https://agentmods.dev/badge/commands/dylanroscover/embody/status.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.00133 |
| Opus 5.5 | $0.00000 | $0.00053 |
| Sonnet 5.5 | $0.00000 | $0.00027 |
| Haiku 4.5 | $0.00000 | $0.00013 |
Grade A, and why
status 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 1mo 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
Perform a quick health check of the Embody project:
- Load
/mcp-tools-referenceif this is the first MCP call - Get TD info via
get_td_infoto confirm Envoy is connected - Run
get_externalizationsto check externalization state - report any dirty (unsaved) operators - Run
get_op_errorswithrecurse=trueon the root to find any errors in the network - Check
dev/logs/for recent ERROR or WARNING entries - Report a concise summary: TD version, Envoy status, externalization health, and any active errors
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.
- 1mo ago First seen · 9 lines · 0 tokens per session scan A bf8700aa3ed2
status is a command published in the GitHub repository dylanroscover/Embody (205 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 133 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-30.
Other commands, from other repositories
sugar-review
Review and manage pending Sugar tasks interactively.
sugar-status
View Sugar system status, task queue, and execution metrics.
sugar-task
Create a comprehensive Sugar task with rich context and metadata.
sugar-context
Load project context from Sugar's memory at session start.
codev
The codev command manages project setup, maintenance, and framework-level operations.
add-tool
Build a new UEFN Toolbelt tool named "$ARGUMENTS". Follow the tool-developer agent workflow exactly.