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 skills/mendixlabs/mxcli/business-eventsnpx skills add mendixlabs/mxcli --skill business-eventsgit clone --depth 1 https://github.com/mendixlabs/mxcliWhat 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.00050 | $0.01180 |
| Opus 5 | $0.00025 | $0.00590 |
| Sonnet 5 | $0.00010 | $0.00236 |
| Haiku 4.5 | $0.00005 | $0.00118 |
Grade A, and why
business-events 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Events
When to Use This Skill
Use this skill when the user wants to:
- Define event-driven APIs using Kafka/message brokers
- Create business event services that publish events
- View or describe existing business event services
- Set up publish/subscribe message channels
Commands
View Business Events
-- List all business event service documents
show business event services;
-- Filter by module
show business event services in MyModule;
-- List all business event client documents (future)
show business event clients;
-- List individual messages across all services
show business events;
-- Filter messages by module
show business events in MyModule;
-- Full MDL description (round-trippable)
describe business event service Module.ServiceName;
Create a Business Event Service
create business event service Module.CustomerEventsApi
(
ServiceName: 'CustomerEventsApi',
EventNamePrefix: 'com.example'
)
{
message CustomerChangedEvent (CustomerId: long) publish
entity Module.PBE_CustomerChangedEvent;
message AddressChangedEvent (AddressId: long) publish
entity Module.PBE_AddressChangedEvent;
};
Create or Modify (Idempotent Update — Preferred)
Preserves the existing UUID so other documents that reference this service remain valid.
OR REPLACE is accepted as a synonym.
create or modify business event service Module.CustomerEventsApi
(
ServiceName: 'CustomerEventsApi',
EventNamePrefix: ''
)
{
message CustomerChangedEvent (CustomerId: long) publish
entity Module.PBE_CustomerChangedEvent;
};
Drop a Business Event Service
drop business event service Module.CustomerEventsApi;
Message Definition Syntax
message <MessageName> (<AttrName>: <type>, ...) publish|subscribe
[entity <Module.EntityName>]
[microflow <Module.MicroflowName>];
Supported Attribute Types
string- Textinteger- 32-bit integerlong- 64-bit integerdecimal- Precise decimal numberboolean- True/falsedatetime- Date and time
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 · 159 lines · 50 tokens per session scan A 78dac2f6c738
business-events is a skill published in the GitHub repository mendixlabs/mxcli (115 stars, last pushed 3d ago), licensed Apache-2.0. It adds 50 tokens to every session and 1,180 once invoked, about $0.0003 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-30.
Other skills, from other repositories
zh-output-example
Reviews Chinese skill documentation for publication readiness. Invoke when the user asks in Chinese to review a skill.
review-offered-task
Review a task that has been offered to you and decide whether to accept or reject it.
aidd-dev:08:for-sure
Iterative agent loop that tracks attempts and retries until a success condition is met. Use when the user says "for sure", "make sure", "keep trying until", "loop until done", "don't stop until", or needs guaranteed completion of a task with explicit success criteria.
Swift Performance Optimization Skill
Use when investigating measured Swift or Apple-platform regressions in CPU, memory, launch, scrolling, animation hitches, image processing, energy, networking, or concurrency, or when designing performance tests and Instruments experiments. Do not use for speculative micro-optimization, ordinary refactoring, or a…
examples-qa
Verify Instructor behavior through the repository's ./examples/ suite in pass, live record, or hermetic replay mode. Use when running selected examples or the corpus, capturing and reusing recorded LLM HTTP responses, diagnosing hub results, or distinguishing real errors, assertion failures, skipped examples, and…
systematic-debugging
Root-cause a bug already in front of you, instead of guessing at fixes. Use on triggers like "root cause this", "why is this failing", "debug systematically", "this test is flaky", "it works locally but not in CI", or when a fix attempt has already failed once. Enforces a phased evidence-first process before any code…