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 dylanroscover/Embody --skill testinggit 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/skills/dylanroscover/embody/testing)<a href="https://agentmods.dev/skills/dylanroscover/embody/testing"><img src="https://agentmods.dev/badge/skills/dylanroscover/embody/testing/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/dylanroscover/embody/testing"><img src="https://agentmods.dev/badge/skills/dylanroscover/embody/testing.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.00077 | $0.02098 |
| Opus 5.5 | $0.00031 | $0.00839 |
| Sonnet 5.5 | $0.00015 | $0.00420 |
| Haiku 4.5 | $0.00008 | $0.00210 |
Grade A, and why
testing 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 3d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing: a show is verified by running it, not by looking at it once
A network that renders one good frame has passed one test of eight. Shows fail at hour three, not minute one: a buffer that grows 2 MB a minute, a feedback loop that drifts, an absTime that loses precision, a cook cascade that only starts when the cue list reaches scene 4. Every stable installation you have seen was soaked before it was trusted. Testing is not a phase after building; it is how you know the build is real.
The ladder
| Rung | Question | Evidence |
|---|---|---|
| 1 Structure | Does the network I meant exist? | get_network_layout (no overlaps, forward wires, docks hugged), get_connections, read_tdxn for the authored state |
| 2 Errors | Is anything red? | get_op_errors with recurse=true: cook errors, kind: 'script' tracebacks AND shaderErrors. Fix, re-run, clean |
| 3 Frame | Does it render what I intended? | capture_top on the output (a Quality: FAIL is black or flat and never passes); capture_op for every other family; sample_grid for numbers |
| 4 Motion | Does it animate, and settle? | Two captures seconds apart must differ; feedback and particles judged after settling; a loop wrap watched twice (/visual-aesthetics) |
| 5 Data | Are the values right, not just present? | get_chop_data (per-channel stats, compare_to), get_dat_content(format='stats'), get_pop_data metadata. Never a blind dump |
| 6 Performance | Does it hold frame rate with headroom? | get_project_performance before and after every heavy step, against the performance.md thresholds |
| 7 Soak | Does it STAY right for as long as the show runs? | run_soak_test for minutes to hours: PASS means flat memory, zero drops, fps above the floor |
| 8 End to end | Does the show sequence work, cue by cue, on the show machine? | Drive the real inputs and assert the outputs at each step; relay to the show machine with Convoy |
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.
- 3d ago First seen · 72 lines · 77 tokens per session scan A 1f62d650fa6a
testing is a skill published in the GitHub repository dylanroscover/Embody (182 stars, last pushed 4d ago), licensed MIT. It adds 77 tokens to every session and 2,098 once invoked, about $0.0003 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-09-27.
Other skills, from other repositories
ganju-cli
Write, test, deploy and debug Ganju custom tools (Functions) with the ganju CLI and the @ganju/sdk handler API. Use this whenever the user works in a folder with a ganju.json, imports @ganju/sdk or defineTool, mentions @ganju/cli or any ganju command (init, link, build, test, deploy, logs, versions, rollback, secret…
elicitation-scenarios
Drive the elicitation tester's scenario catalogue over the modern protocol, where input requests arrive in the tool result and are answered from the chat.
elicitation-scenarios-legacy
Drive the elicitation tester's scenario catalogue over the legacy protocol, where the server sends elicitation requests during the call instead of returning them in the result.
verify-packaged-assets
Verify that a packaged reference can be read and a packaged script can execute in the conversation sandbox.
agentcore-investigation
Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.
amazon aurora dsql
Deprecated compatibility redirect for Aurora DSQL guidance. Use when a request concerns DSQL, Aurora DSQL, distributed SQL, DSQL schemas, migrations, queries, authentication, performance, or application development.