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 mendixlabs/mxcli --skill analyze-runtimegit clone --depth 1 https://github.com/mendixlabs/mxcliWrote 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/mendixlabs/mxcli/analyze-runtime)<a href="https://agentmods.dev/skills/mendixlabs/mxcli/analyze-runtime"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/analyze-runtime/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/mendixlabs/mxcli/analyze-runtime"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/analyze-runtime.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00068 | $0.03151 |
| Opus 5.5 | $0.00027 | $0.01260 |
| Sonnet 5.5 | $0.00014 | $0.00630 |
| Haiku 4.5 | $0.00007 | $0.00315 |
Grade A, and why
analyze-runtime scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://127.0.0.1:8090/prometheus | grep -E 'connectionbus_|handler_requests|sessions_|taskqueue_' How it starts
The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find it fast
sed -n '<from>,<to>p' SKILL.md one section rather than reading the file;
./mxcli syntax <topic> answers how do I write this for a fraction of either.
| lines | section |
|---|---|
| 27-41 | Overview |
| 42-51 | When to Use This Skill |
| 52-136 | 1. Logs — the first stop for errors |
| 137-151 | 2. Metrics — throughput and database pressure |
| 152-175 | 3. Traces — where the time goes |
| 176-193 | 4. Model shape — the catalog |
| 194-221 | 5. The app warehouse — join the signals (external DuckDB) |
| 222-229 | Known gap: logs ↔ traces |
| 230-239 | Decision guide |
| 240-245 | See Also |
Analyze an App's Runtime Behavior — Logs, Metrics, Traces, Catalog
Overview
When you need to understand what an app actually does at runtime — why a page is slow, which microflow dominates cost, what hits the database, whether an error is network or logic — the signals live in four places. This skill is the procedure for collecting them and, crucially, joining them, because the useful questions cross sources that no single tool answers alone.
| Signal | Where | How you get it |
|---|---|---|
Logs (server stack traces + your LOG output) |
<projectDir>/.mxcli/runtime.log |
mxcli run --local tees it automatically |
| Metrics (throughput, DB counts, sessions, queues) | /prometheus on the admin port |
mxcli run --local --metrics |
| Traces (per-microflow / per-activity spans + timings) | console→runtime.log, or an OTLP collector |
mxcli run --local --trace / --trace-otlp |
| Model shape (activities, complexity, refs, XPath) | .mxcli/catalog.db (SQLite) |
mxcli … "refresh catalog full" then SELECT … FROM CATALOG.* |
When to Use This Skill
- A page/microflow is slow and you need to find where the time goes.
- You want to know which entities/queries the app actually hits, and how often.
- A server-side error shows only a generic dialog in the browser.
- You're profiling and need a flame chart, or want cost correlated with model shape.
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.
- 5d ago Changed · +19 lines 81d71e31f71a
- 1mo ago First seen · 227 lines · 68 tokens per session scan A d2844227fb74
analyze-runtime is a skill published in the GitHub repository mendixlabs/mxcli (130 stars, last pushed yesterday), licensed Apache-2.0. It adds 68 tokens to every session and 3,151 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
codegraph
Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection…
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
memory-leak-debug
Diagnose memory leaks in the Qwen Code CLI using heap snapshots and the chrome-devtools CLI. Use when investigating high memory usage, unbounded growth, or suspected object retention issues.
bugfix
Fix a bug from a GitHub issue, following the reproduce-first workflow. Use when the user asks to fix a bug, investigate a GitHub issue, or debug a user-reported problem. Takes a GitHub issue URL or number as input.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.