I have a small okx-hol-guard Agent Skill ready that would add HOL Guard as an optional local runtime boundary before state-changing OKX workflows.
The intended shape follows this repo’s existing skill model rather than changing any OKX CLI semantics:
- install and initialize
hol-guard on a supported local coding-agent harness
- run the actual OKX workflow from the protected harness
- preserve the existing OKX skills as authoritative for authentication, demo/live mode, sizing, instrument selection, confirmations, and all
okx / MCP syntax
- stop on Guard deny/review/error/unavailable states instead of suggesting an unprotected fallback
- never put OKX credentials into prompts, Guard receipts, or logs
- avoid duplicating the existing OKX command tables
The contribution is already prepared here:
kantorcodes@7335e9b
It uses the repository’s required skills/<name>/SKILL.md shape, license: MIT, required metadata, a demo/live section, routing to the existing OKX skills, and a focused Guard operation flow. HOL Guard commands were checked against its maintained canonical skill.
If this placement fits the project, I’m happy for the prepared change to be reviewed as the basis for the repository’s preferred contribution path. I did not perform a live or demo trade for this documentation-only contribution, so I’m not claiming that runtime test.
Affiliation: I maintain HOL Guard / Hashgraph Online. AI assistance was used to prepare the focused text; I reviewed the scope against the current OKX skill and HOL Guard command contracts.
I have a small
okx-hol-guardAgent Skill ready that would add HOL Guard as an optional local runtime boundary before state-changing OKX workflows.The intended shape follows this repo’s existing skill model rather than changing any OKX CLI semantics:
hol-guardon a supported local coding-agent harnessokx/ MCP syntaxThe contribution is already prepared here:
kantorcodes@7335e9b
It uses the repository’s required
skills/<name>/SKILL.mdshape,license: MIT, required metadata, a demo/live section, routing to the existing OKX skills, and a focused Guard operation flow. HOL Guard commands were checked against its maintained canonical skill.If this placement fits the project, I’m happy for the prepared change to be reviewed as the basis for the repository’s preferred contribution path. I did not perform a live or demo trade for this documentation-only contribution, so I’m not claiming that runtime test.
Affiliation: I maintain HOL Guard / Hashgraph Online. AI assistance was used to prepare the focused text; I reviewed the scope against the current OKX skill and HOL Guard command contracts.