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 agentmods add agents/jordnlvr/mendixtoolkit/mendix-expertgit clone --depth 1 https://github.com/jordnlvr/MendixToolkitWhat 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 | $0.00071 | $0.01258 |
| Opus 5 | $0.00036 | $0.00629 |
| Sonnet 5 | $0.00014 | $0.00252 |
| Haiku 4.5 | $0.00007 | $0.00126 |
Grade A, and why
mendix-expert 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 First seen · 82 lines · 71 tokens per session scan A 561c4e31190d
mendix-expert is an agent published in the GitHub repository jordnlvr/MendixToolkit (2 stars, last pushed 3mo ago), with no licence file. It adds 71 tokens to every session and 1,258 once invoked, about $0.0004 per session on Opus 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-31.
Other agents, from other repositories
issue-analyzer
Analyzes a GitHub issue, investigates the relevant codebase, and posts a structured analysis back to the ticket via the GitHub CLI. Use when someone says "analyze issue #N", "investigate this issue", "look into #N", "research issue", or asks for a deep-dive on a bug report or feature request. Always invoke this agent…
Architecture and Design
Cross-language architectural guidance for designing scalable, maintainable, and performant code. Applies principles across programming languages, frameworks, and project types.
sql-developer
Use this agent when the user explicitly requests help with SQL Server or T-SQL development tasks. This includes writing queries, creating stored procedures, optimizing performance, analyzing execution plans, or reviewing SQL code. Context: User is starting a new database project and needs help with queries. user…
swift-developer
Use this agent when the user explicitly requests help with Swift, iOS, or macOS development tasks. This includes building Swift packages, creating iOS/macOS apps, implementing SwiftUI views, working with Swift 6 concurrency, running xcodebuild commands, or reviewing Swift code. Context: User is starting a new iOS…
powershell-developer
Use this agent when the user explicitly requests help with PowerShell development tasks. This includes writing PowerShell scripts, creating modules, building Windows Forms/WPF GUIs, working with PowerShell Gallery, or reviewing PowerShell code. Context: User is starting a new PowerShell project and needs help setting…
rust-developer
Use this agent when the user explicitly requests help with Rust development tasks. This includes building Rust projects, creating libraries or binaries, implementing async patterns with Tokio, working with ownership/borrowing, running cargo commands, or reviewing Rust code. Context: User is starting a new Rust project…