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/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/commands/mendixlabs/mxcli/refresh-catalog)<a href="https://agentmods.dev/commands/mendixlabs/mxcli/refresh-catalog"><img src="https://agentmods.dev/badge/commands/mendixlabs/mxcli/refresh-catalog/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/mendixlabs/mxcli/refresh-catalog"><img src="https://agentmods.dev/badge/commands/mendixlabs/mxcli/refresh-catalog.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.00010 | $0.00384 |
| Opus 5.5 | $0.00004 | $0.00154 |
| Sonnet 5.5 | $0.00002 | $0.00077 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
refresh-catalog 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
Refresh Catalog
Rebuild the catalog database for querying project metadata.
Commands
-- Fast mode (metadata only, ~5 seconds)
REFRESH CATALOG;
-- Full mode (includes activities, widgets, and strings FTS table)
REFRESH CATALOG FULL;
-- Source mode (includes full + MDL source FTS table)
REFRESH CATALOG SOURCE;
-- Force rebuild (ignores cache)
REFRESH CATALOG FULL FORCE;
When to Use
- After making changes to the project
- Before running catalog queries
- When exploring a new project
- Use FULL mode before using SEARCH command
- Use SOURCE mode for searching MDL definitions
The cache's mode is sticky. Once a project has a FULL or SOURCE cache, a plain
REFRESH CATALOG rebuilds at that level rather than dropping to FAST, and a
command that needs less (mxcli check -p, show structure, describe) never
replaces it with a narrower one. To go back to a cheaper level, delete
.mxcli/catalog.db and refresh.
Example Queries After Refresh
-- Find entities
SELECT Name, AttributeCount FROM CATALOG.ENTITIES WHERE ModuleName = 'Sales';
-- Find microflows
SELECT QualifiedName, ParameterCount FROM CATALOG.MICROFLOWS WHERE Name LIKE '%Customer%';
-- Find pages
SELECT Name, WidgetCount FROM CATALOG.PAGES;
-- Full-text search (requires FULL mode)
SEARCH 'validation';
-- Raw FTS query on strings
SELECT * FROM CATALOG.STRINGS WHERE strings MATCH 'error';
-- Raw FTS query on source (requires SOURCE mode)
SELECT * FROM CATALOG.SOURCE WHERE source MATCH 'CREATE ENTITY';
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 Changed · +6 lines d003e1524056
- 1mo ago First seen · 55 lines · 10 tokens per session scan A 694d240c438d
refresh-catalog is a command published in the GitHub repository mendixlabs/mxcli (132 stars, last pushed 2d ago), licensed Apache-2.0. It adds 10 tokens to every session and 384 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
analyze
Full GoSQLX analysis of a SQL string or .sql file (validity, metadata, security, lint, formatting).
format
Format a SQL string or .sql file with GoSQLX.
security
Scan a SQL string, .sql file, or SQL-building source file for injection risks with GoSQLX.
toh-connect
Connect app to Supabase backend with schema and RLS policies.
hatch3r-workflow
Guided development lifecycle with 4 phases (Analyze, Plan, Implement, Review) and scale-adaptive Quick Mode for small tasks; --plan-file executes an approved plan document without re-deriving it.
hatch3r-incident-response
Drive a live production incident through a structured lifecycle -- triage + topology, bounded-autonomy mitigation, stakeholder communication, then a blameless post-mortem with runbook -- via delegated sub-agents.