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-attest-creategit 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-attest-create)<a href="https://agentmods.dev/skills/sageox/ox/ox-attest-create"><img src="https://agentmods.dev/badge/skills/sageox/ox/ox-attest-create.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00082 | $0.00330 |
| Opus 5 | $0.00041 | $0.00165 |
| Sonnet 5 | $0.00016 | $0.00066 |
| Haiku 4.5 | $0.00008 | $0.00033 |
Grade A, and why
ox-attest-create 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
Create evidence, not a decorative stamp
- Start with
ox attest proof <capability>and read the customer claim, current verdict, and any prior evidence. - Make the promised behavior fail in a way that lands on the claim step; save the unedited failure text and its run ID.
- Restore the behavior, run the same scenario green, and retain that run ID.
- Describe the break in the language of the customer's promise. Name only product surfaces the run actually exercised.
- Use
ox attest recordwith both run IDs, the verbatim red failure, the failed step, and the exercised surfaces. If the evidence is ambiguous or incomplete, record that honestly rather than forcing a clean verdict. - Run
ox attest statusandox attest check --jsonafterward. Publish only evidence that remains current and explain any stale or unknown result.
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 · 29 lines · 82 tokens per session scan A 212b5437afcb
ox-attest-create is a skill published in the GitHub repository sageox/ox (51 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 330 once invoked, about $0.0004 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 skills, from other repositories
intuitive-tests
Use this skill whenever the user asks about unit test best practices, test organization, flat test suites, redundant tests, test refactors, pytest/JUnit/Jest/xUnit layout, test taxonomy, flaky tests, coverage quality, fixtures, mocks, parametrization, pruning existing UTs, or "which tests are worth keeping." It…
browser-automation
Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, and anti-detection patterns. This skill covers Playwright (recommended) and Puppeteer, with patterns for testing, scraping…
exploit-xss
Cross-site scripting (XSS) vulnerability detection and exploitation. Supports reflected XSS, stored XSS, DOM-based XSS, and blind XSS testing. Use this skill when user mentions XSS, cross-site scripting, script injection, or needs to test JavaScript injection in parameters, forms, headers, or DOM sources.
visual-verification
Use for any UI/web project — make the verify gate cover more than unit tests by composing a pipeline (types → unit → design-scan → flow-smoke) and running the built-in yoke flow-smoke gate (landmark + zero console errors + screenshot proof to .yoke/proof/ /, video kept on failure). Catches the unwired-page /…
ab-scripting-feature-dev
Generates an AgenticBrowser Scripting DSL orchestration that implements a feature end-to-end — plan (if needed), TDD implementation, tests, and a lint/style-guide review pass — previews it as docs/scripting-features/feature- .scripting.md, and on user approval runs it via st-eval. Use this whenever the user wants to…
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.