Borrowing it
Nothing to install: this file belongs to dynamics365ninja/d365fo-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dynamics365ninja/d365fo-mcp-server/main/.claude/commands/eval-run.mdgit clone --depth 1 https://github.com/dynamics365ninja/d365fo-mcp-serverWrote 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/dynamics365ninja/d365fo-mcp-server/eval-run)<a href="https://agentmods.dev/commands/dynamics365ninja/d365fo-mcp-server/eval-run"><img src="https://agentmods.dev/badge/commands/dynamics365ninja/d365fo-mcp-server/eval-run.svg" alt="Measured on agentmods" 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.00027 | $0.00215 |
| Opus 5 | $0.00014 | $0.00108 |
| Sonnet 5 | $0.00005 | $0.00043 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
eval-run 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 7d 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
Launch the eval-implementer subagent (Task tool, subagent_type: eval-implementer)
to run this eval case through the grounded MCP tool path on the VM:
Case id: $ARGUMENTS
First read eval/cases/$ARGUMENTS.json. The subagent carries the full loop
(isolate → implement grounded-only → static gate → build → golden/SysTest oracle
via npm run eval:score → write corpus record → roll back → triage hypothesis).
It requires the d365fo MCP tools connected in full mode on the VM and pins all
writes to the Contoso sandbox — if those tools are not available, it will say so
and stop. Relay the corpus record and pass/fail verdict back to me.
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.
- 7d ago First seen · 18 lines · 27 tokens per session scan A cd9869022a28
eval-run is a command published in the GitHub repository dynamics365ninja/d365fo-mcp-server (138 stars, last pushed 2d ago), licensed MIT. It adds 27 tokens to every session and 215 once invoked, about $0.0001 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 commands, from other repositories
add-tests
Generate comprehensive tests for a component or API endpoint.
review-before-deploy
Execute comprehensive pre-deployment review using code-review-agent with all relevant platform agents. Run complete deployment readiness checklist: verify all tests pass (unit, integration, E2E), security audit clean (no Critical/High issues), performance benchmarks met (Lighthouse > 90), TypeScript compilation…
paul:verify
Guide manual user acceptance testing of recently built features.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
ui-snapshot.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
journey-audit
Outside-in product audit as a deep session — 7 read-only roles check what the site promises against what the code does, what a user experiences, what arrives by mail, and what the data says is used. Writes a dossier; needs a per-repo journey-manifest.