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/Xiaoyun-0922/openmarxWrote 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/xiaoyun-0922/openmarx/essence)<a href="https://agentmods.dev/commands/xiaoyun-0922/openmarx/essence"><img src="https://agentmods.dev/badge/commands/xiaoyun-0922/openmarx/essence.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.00035 | $0.00388 |
| Opus 5 | $0.00017 | $0.00194 |
| Sonnet 5 | $0.00007 | $0.00078 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
essence 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 8d 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
Activate the marx skill and distinguish surface symptoms from root cause.
Response language policy:
- Match the user's language.
- Keep required contract labels exactly:
已检查证据:,未检查项目证据:,实践方案, and验证标准. - Provide bilingual output only when explicitly requested.
Evidence pass:
- For project/repository/GitHub/adoption tasks, inspect local evidence first.
- Start with
已检查证据or未检查项目证据. - First visible output line must be either
已检查证据:or未检查项目证据:before any title, table, horizontal rule, or summary. Use an ASCII colon:, not a full-width Chinese colon：. Do not use variants such as已检查项目证据:. - Do not start with a horizontal rule, generic title, or
证据表; the evidence line comes first.
Evidence freshness:
- Mark prior-turn facts as reused evidence, not freshly inspected evidence.
- If a concrete implementation target matters, inspect it this turn or label it as an assumption.
Required final sections:
- Include
实践方案and验证标准exactly in every project-grounded answer. - Do not rename these sections to "next steps", "建议", "接下来的路", or "最小下一步验证".
验证标准must contain an observable pass/fail rule or measurable metric.
Output focus:
- 表面现象
- 可能本质
- 根因候选
- 区分根因所需证据
- 最小下一步验证
User request: $ARGUMENTS
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.
- 8d ago First seen · 37 lines · 35 tokens per session scan A 479ccdbd41b4
essence is a command published in the GitHub repository Xiaoyun-0922/openmarx (5 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 388 once invoked, about $0.0002 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 commands, from other repositories
widget-validate
Validates SAC custom widget JSON metadata and JavaScript structure for correctness and best practices.
sac-debug
Debug SAC script issues with guided analysis and common error resolution.
sqlscript-validate
Validates SQLScript code for syntax, patterns, and best practices with auto-fix capability.
cap-troubleshooter
Diagnostic guide for common CAP errors and issues with solutions.
bas-dev-space-diagnose
Diagnose SAP Business Application Studio dev space setup, extensions, generators, runtime tools, and project readiness.
btp-logging-ingestion-check
Check SAP Cloud Logging ingestion setup, source bindings, OpenTelemetry paths, and missing log or metric symptoms.