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 resolve-forward-referencesgit 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/resolve-forward-references)<a href="https://agentmods.dev/skills/mendixlabs/mxcli/resolve-forward-references"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/resolve-forward-references/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/resolve-forward-references"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/resolve-forward-references.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.00049 | $0.02535 |
| Opus 5.5 | $0.00020 | $0.01014 |
| Sonnet 5.5 | $0.00010 | $0.00507 |
| Haiku 4.5 | $0.00005 | $0.00253 |
Grade A, and why
resolve-forward-references 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 2d 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 — 342 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 |
|---|---|
| 26-52 | Why Forward References Fail |
| 53-70 | The Placeholder Pattern |
| 71-137 | Pattern 1 — Shared Navigation Snippet (most common) |
| 138-185 | Pattern 2 — Page References Another Page (new/edit from overview) |
| 186-218 | Pattern 3 — Microflow References a Page Not Yet Created |
| 219-237 | Ordering Rules for Dependency-Free Scripts |
| 238-261 | Choosing Between CREATE OR MODIFY and ALTER SNIPPET |
| 262-336 | Script Template for a Full CRUD Module |
| 337-341 | Related Skills |
Resolving Forward References in MDL Scripts
Why Forward References Fail
MDL script execution is sequential and immediate — each CREATE statement commits
its document to the project database before the next statement runs. When a document is
being built, all its references (snippets, pages, microflows) are resolved against the
database at that moment. A reference to something defined later in the same script fails
because it is not in the database yet.
Error: snippet not found: MyModule.NavMenu
This applies to the following reference types:
| Reference | In | Fails when |
|---|---|---|
snippetcall |
page / snippet | snippet created after the page |
show page in action |
page / snippet | page created after the page that references it |
SHOW PAGE |
microflow | page created after the microflow |
call microflow |
microflow | callee created after the caller — only under exec --continue-on-error, the REPL or -c. Plain mxcli exec rolls back on failure and resolves the call against every flow the script declares, so mutual recursion needs no stub (mendixlabs/mxcli#1405) |
Note:
SHOW PAGEinside a microflow body resolves the page reference at microflow-creation time, not at invocation time. If the target page doesn't exist yet, the microflow creation fails.
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.
- 2d ago Changed 45e5780c2084
- 5d ago Changed · +18 lines 76089c0468c4
- 7d ago Changed · +3 lines f73ac2c1ce08
- 15d ago Changed · -13 lines 605f523d692f
- 16d ago Changed 517157b33abd
- 1mo ago First seen · 334 lines · 49 tokens per session scan A e5a6d80213cf
resolve-forward-references is a skill published in the GitHub repository mendixlabs/mxcli (131 stars, last pushed yesterday), licensed Apache-2.0. It adds 49 tokens to every session and 2,535 once invoked, about $0.0002 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-03.
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.