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 sageox/ox --skill ox-cli-initgit clone --depth 1 https://github.com/sageox/oxWrote 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/sageox/ox/ox-cli-init)<a href="https://agentmods.dev/skills/sageox/ox/ox-cli-init"><img src="https://agentmods.dev/badge/skills/sageox/ox/ox-cli-init/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/sageox/ox/ox-cli-init"><img src="https://agentmods.dev/badge/skills/sageox/ox/ox-cli-init.svg" alt="Reviewed on agentmods" width="80" 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.00011 | $0.00268 |
| Opus 5 | $0.00005 | $0.00134 |
| Sonnet 5 | $0.00002 | $0.00054 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
ox-cli-init 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 2d 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
Explicit invocation only. Run this when the user asks for it by name. It performs a lifecycle or diagnostic action with side effects, so never invoke it on your own initiative.
Use when:
- Setting up SageOx in a new repository for the first time
- Configuring ox CLI integration with your coding agent
- Installing hooks for automatic guidance loading
Keywords: init, initialize, setup, install, configure, first-time, onboarding
Common Issues
Already initialized
Symptom: SageOx already initialized in this repository
Solution: This is fine - ox is ready to use. Run ox agent prime to load guidance
Permission denied
Symptom: Cannot create .sageox directory Solution: Check write permissions for the repository directory
Not a git repository
Symptom: not a git repository
Solution: Initialize git first: git init
$ox init
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.
- 2d ago First seen · 36 lines · 11 tokens per session scan A 10cca99a3f2a
ox-cli-init is a skill published in the GitHub repository sageox/ox (51 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 268 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-09-08.
Other skills, from other repositories
commit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
create-pr
Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.
intuitive-squash
Squash local GSD or agent-generated commit history into a clean, reviewable story while preserving important fixes. Use when the user asks to squash commits, clean git history, compress phase commits, prepare a branch before PR, compare aggressive vs moderate squash options, or preserve hotfix/security commits during…
codex-review
Professional code review with auto CHANGELOG generation, integrated with Codex AI.
intuitive-port-worktree
Port changes from one git worktree or checkout into the default repository folder's current branch, then by default sync the result to the remote default branch when everything is clean. Use when the user asks to move, copy, transfer, transplant, cherry-pick, apply a patch, or port worktree changes into the…
chinese-git-workflow
A Git workflow guide tailored to Chinese-hosted platforms such as Gitee, Coding.net, and GitLab, including their code-review and build systems.