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 greedychipmunk/agent-skills --skill elizaos-runtime-diagnosticsgit clone --depth 1 https://github.com/greedychipmunk/agent-skillsWrote 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/greedychipmunk/agent-skills/elizaos-runtime-diagnostics)<a href="https://agentmods.dev/skills/greedychipmunk/agent-skills/elizaos-runtime-diagnostics"><img src="https://agentmods.dev/badge/skills/greedychipmunk/agent-skills/elizaos-runtime-diagnostics/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/greedychipmunk/agent-skills/elizaos-runtime-diagnostics"><img src="https://agentmods.dev/badge/skills/greedychipmunk/agent-skills/elizaos-runtime-diagnostics.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.00066 | $0.01164 |
| Opus 5.5 | $0.00026 | $0.00466 |
| Sonnet 5.5 | $0.00013 | $0.00233 |
| Haiku 4.5 | $0.00007 | $0.00116 |
Grade A, and why
elizaos-runtime-diagnostics 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
elizaOS Runtime Diagnostics
Establish version and authority
Identify the installed release/commit, launch mechanism, OS, host type, actual API origin, database backend, intended provider, and first error timestamp. Confirm ownership and permission to inspect that instance. Distinguish a core-only embedding, standalone agent, app/desktop host, Cloud container, and Cloud thin client. Do not assume a thin client has a local runtime.
Read version and command provenance before
suggesting commands. This baseline is develop commit
eb9a6f7d3ccc46d3ff9d173383cff900004738c9 (2026-10-15), not legacy 1.x CLI docs.
Recheck corresponding source when the installed version differs. Do not install,
upgrade, build, or execute upstream code just to diagnose it.
Start offline
-
Ask for the precise failure and a small redacted existing error window. Do not request complete environment/configuration/log dumps or provider keys.
-
Inspect manifest metadata and only explicitly requested environment-variable presence with the bundled Python-stdlib helper, if useful:
python3 scripts/offline_report.py --manifest /approved/checkout/package.json \ --env OPENAI_API_KEY --env POSTGRES_URLResolve the script relative to this skill, not the target repo. With no arguments it inspects nothing. It never reads environment values,
.env, configuration, logs, or databases; executes no subprocesses; and makes no network requests. Manifest reads are explicit, bounded, regular-file-only, and reject symlink components. Use trusted stable parent directories; this is not a sandbox against concurrent directory replacement. Presence means name exists, even if empty; it does not establish validity, activation, or runtime inheritance. Only known script names, never bodies, are reported. Exit 0 means the requested inventory was built, 1 means at least one manifest could not be inspected, and 2 means invalid arguments/limits. None proves runtime readiness or credential validity. -
Do not infer that a core runtime automatically reads arbitrary process environment. Trace host configuration, plugin configuration, and provider registration at the installed revision before changing a setting.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 103 lines · 66 tokens per session scan A 5efcf751a4f5
elizaos-runtime-diagnostics is a skill published in the GitHub repository greedychipmunk/agent-skills (22 stars, last pushed yesterday), licensed MIT. It adds 66 tokens to every session and 1,164 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-10-16.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…