Thin Codex skill shim for node_bus_audit_compute. Use when auditing OmniNode event-bus topic registry and contract wiring health.
75%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./plugins/onex/skills/bus-audit/SKILL.mdThis skill is a thin Codex runtime adapter shim over the OmniMarket
node_bus_audit_compute node. The node owns event registry parsing, contract
wiring checks, and finding classification. Do not add Kafka probing, grep
fallbacks, or inline audit logic to this skill.
This section is generated from the Codex adapter contract and the target node contract. Keep the two surfaces distinct:
bus_audit_computescripts/run_codex_runtime_request.pyonex.cmd.omnimarket.pattern-b-dispatch.v1onex.evt.omnimarket.pattern-b-dispatch-completed.v1--compile-only to validate the request and binding
without publishing an event or starting a runtime. This is adapter preflight,
not evidence that a target runtime executed the command.runtime_evidence.runtime_observation and
runtime_evidence.adapter_dispatch_binding; compile-only is UNOBSERVED
with reason compile_only.runtime_evidence.schema_version is
runtime-evidence/v2; v2 requires runtime_observation and carries the
resolved node contract under adapter_dispatch_binding.node_contract.adapter_dispatch_binding reports
adapter_command_topic, requested_response_topic,
selected_terminal_topic, and terminal_selection (NODE_CONTRACT,
DIRECT_DELEGATE_SKILL_CONTRACT, or EXPLICIT_RESPONSE_OVERRIDE); its
node_contract is the resolved, typed contract binding.node_bus_audit_computenode_bus_audit_computeonex.cmd.omnimarket.bus-audit-start.v1onex.evt.omnimarket.bus-audit-completed.v1The skill must use the request wrapper for dispatch. It must not publish the target node command topic directly as its generic adapter transport; the target topics above are contract metadata selected by the runtime adapter.
| Argument | Description | Default |
|---|---|---|
scope | Operator-facing audit scope | local |
registry_path | Optional event registry YAML path | Node default |
contract_roots | Contract roots or contract.yaml files to scan | Node default |
failures_only | Return only error findings | false |
verbose | Include informational findings | false |
skip_daemon | Skip live daemon checks | false |
broker | Broker hint for future live sampling | Omitted |
sample_count | Requested sample count for future live sampling | 20 |
dry_run | Run without side effects | false |
target_runtime_address | Optional runtime://... runtime target | Uses ONEX_TARGET_RUNTIME_ADDRESS when set |
Run from the omnimarket repo or an omnimarket worktree:
env -u PYTHONPATH uv run python scripts/run_codex_runtime_request.py \
--command-name "bus_audit_compute" \
--payload '<json-payload>' \
--timeout-ms 30000If the user supplies a runtime://... target, add
--target-runtime-address '<runtime-address>' to the request command. If the
argument is omitted, the wrapper uses ONEX_TARGET_RUNTIME_ADDRESS when set.
For event-bus-free preflight, add --compile-only. This validates the payload,
command topic, response topic, correlation id, timeout, and target runtime
address without publishing to Kafka or starting a runtime.
Map user inputs into a JSON payload using the same field names:
scoperegistry_pathcontract_rootsfailures_onlyverboseskip_daemonbrokersample_countdry_runIf ok is true and output_payloads is present, treat output_payloads[0]
as the primary node result.
If ok is false, surface error.code and error.message directly.
src/omnimarket/nodes/node_bus_audit_compute/scripts/run_codex_runtime_request.pybus_audit_computeonex.cmd.omnimarket.bus-audit-start.v1onex.evt.omnimarket.bus-audit-completed.v1Prefer output_payloads[0]. Render status, topic counts, contract count,
and findings grouped by severity. All audit behavior is owned by
node_bus_audit_compute.
OmniNode-ai/omnimarket
13a7e30
Also appears in
since Nov 7, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.