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 project-braingit 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/project-brain)<a href="https://agentmods.dev/skills/mendixlabs/mxcli/project-brain"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/project-brain/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/project-brain"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/project-brain.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.00094 | $0.04837 |
| Opus 5.5 | $0.00038 | $0.01935 |
| Sonnet 5.5 | $0.00019 | $0.00967 |
| Haiku 4.5 | $0.00009 | $0.00484 |
Grade A, and why
project-brain 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 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.
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 — 384 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 |
|---|---|
| 49-66 | The rule that makes it work |
| 67-103 | Reading it |
| 104-124 | Writing to it |
| 125-204 | Recording requirements and slices |
| 205-219 | When to capture a decision |
| 220-254 | Recording what is NOT decided |
| 255-274 | Write the anchor, not the name |
| 275-296 | Checking it |
| 297-312 | Size |
| 313-329 | Commands |
| 330-344 | Renaming |
| 345-354 | What not to record |
| 355-380 | Handing a slice to another agent |
| 381-383 | Project brain (mxcli brain init/capture/staged/promote/drop/check/show) |
Project brain
The brain holds what mxcli cannot compute about this project. Two halves:
- Decisions — why a pattern was chosen here, which marketplace version broke what, what a recurring mxbuild error means in this app.
- Open questions — what is not decided yet, so it is not silently forgotten and rediscovered expensively later.
- The plan — the requirements being built from and the slices they are grouped into, when the source is a specification document, a prototype or a conversation rather than GitHub issues.
The plan half matters because hours of work can otherwise leave no trace: a Word document and a chat transcript are not in git, so a session that resumes later has no idea what it was building towards, and neither does the next person.
It lives in docs/brain/, is committed, and is reviewed in a pull request like
any other change.
The rule that makes it work
Anything mxcli can answer does not belong here. Entities, microflows, pages, bindings, references, callers, dead assets — all queryable. A note that transcribes any of them is a note that will disagree with the project the moment someone edits the model, and it will disagree silently.
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 · +23 lines 6b13a130d489
- 16d ago Changed 2d74f904754f
- 24d ago Changed · +4 lines 34d0ab8565bd
- 1mo ago Changed · +17 lines 8efb5de91038
- 1mo ago Changed · +59 lines 4b0627502450
- 1mo ago First seen · 281 lines · 94 tokens per session scan A f4b75c1fbbae
project-brain is a skill published in the GitHub repository mendixlabs/mxcli (131 stars, last pushed yesterday), licensed Apache-2.0. It adds 94 tokens to every session and 4,837 once invoked, about $0.0004 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-05.
Other skills, from other repositories
proactive-agent
Transform AI agents from task-followers into proactive partners that anticipate needs and continuously improve. Now with WAL Protocol, Working Buffer, Autonomous Crons, and battle-tested patterns. Part of the Hal Stack 🦞.
memory-recall
Persistent cross-session memory system with fact extraction, semantic search, and compiled memory layers. Your agent remembers everything across sessions — user preferences, project context, past decisions, personal details. Use when: (1) User references something from a previous conversation, (2) Agent needs project…
session-checkpoint
Re-orient a long, dense, or interruption-prone agent session without replacing the underlying evidence. Use when the user asks for a recap, orientation, simple teaching explanation, or spoken summary; when a session has accumulated many turns or tool calls; before context compaction; or when a Brief-Spec hook says a…
Session Management
Session persistence, resume patterns, event store replay, compaction tuning.
Memory Retrieval
How semantic memory works with compaction and the MemoryStore trait.
memory-continuity
Preserves cross-session continuity with deterministic MEMORY.md, index.md, and snapshot handoffs under .agentic/memories/.