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 agentmods add skills/sageox/ox/ox-pr-headernpx skills add sageox/ox --skill ox-pr-headergit 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-pr-header)<a href="https://agentmods.dev/skills/sageox/ox/ox-pr-header"><img src="https://agentmods.dev/badge/skills/sageox/ox/ox-pr-header.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.00140 | $0.01039 |
| Opus 5 | $0.00070 | $0.00519 |
| Sonnet 5 | $0.00028 | $0.00208 |
| Haiku 4.5 | $0.00014 | $0.00104 |
Grade A, and why
ox-pr-header 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You do not hand-write this markup — ox pr header does. A GitHub PR body is
sanitized harder than repo markdown (no CSS, no styled tables); the line is built
from the exact primitives that survive (<picture> wordmark, <a> links, <sub>
caption). Hand-authoring it is how it silently renders as a bordered table or a
vanished wordmark. Run the command and paste its output verbatim.
When
At PR-creation time, only when SageOx-delivered team context measurably shaped the
work (your contribution score is not none). If SageOx did not shape it, omit both
the header and the SageOx-Session: trailer — publishing SageOx credit for work it
did not influence is the fabrication #809 guards against. When it did shape the work,
the header is the top of the body and the SageOx-Session: trailer stays the
last line (they serve different readers: the header a human, the trailer the
reconciler).
How
-
Gather what the PR credits (you already hold this from your session):
- the plan ids you saved (
pln_…), if any; - the enrichment counts from
ox plan enrich(related sessions / concurrent edits), if any.
- the plan ids you saved (
-
Run the command — the current session is auto-linked; add plans + enrichment:
ox pr header \ --plan pln_4d8e2f --plan pln_1a6b9c \ --prior-art 2 --collisions 1--session <url|ses_id>adds/overrides sessions (default: the live session).--no-statdrops the whisper.--style text|image|autofollowsox config(pr_visuals.style) by default.--jsonreturns the markup plus resolved inputs for verification. -
Paste the output as the FIRST lines of the PR body, above your summary. Write the body via a file, never a heredoc — a heredoc mangles the markup:
ox pr header > body.md printf '\n' >> body.md cat description.md >> body.md # your written summary # ...keep the SageOx-Session: trailer as the last line... gh pr create --body-file body.md
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.
- 5d ago First seen · 81 lines · 140 tokens per session scan A 47113031b1f2
ox-pr-header is a skill published in the GitHub repository sageox/ox (51 stars, last pushed today), licensed MIT. It adds 140 tokens to every session and 1,039 once invoked, about $0.0007 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
qmd
Search the vault using QMD semantic search. Use PROACTIVELY before reading files. Preference order: (1) MCP tools — mcpqmdquery, mcpqmdget, mcpqmdmultiget, mcpqmdstatus — if they appear in your tool menu, use them first; (2) CLI qmd --index ... as fallback; (3) Grep/Glob only when QMD is not installed. Trigger…
obsidian-cli
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their…
unity-vrc-skills-renovator
VRChat skill renovator for knowledge fill, refresh, and quality improvement. Use this skill when updating VRChat skills to new SDK versions, filling missing knowledge, fixing outdated information, or improving skill quality. Targets unity-vrc-udon-sharp and unity-vrc-world-sdk-3 skills. Triggers on: update skills, SDK…
neo4j-snowflake-graph-analytics-skill
Run Neo4j Graph Analytics algorithms (PageRank, Louvain, WCC, Dijkstra, KNN, Node2Vec, FastRP, GraphSAGE) directly inside Snowflake without moving data. Use when running graph algorithms against Snowflake tables via the Neo4j Snowflake Native App ("GDS Snowflake", "graph algorithms in Snowflake", "Neo4j Graph…
neo4j-aura-graph-analytics-skill
Serverless Aura Graph Analytics (AGA) GDS Sessions — covers GdsSessions, AuraGraphDataScience, AuraAPICredentials, DbmsConnectionInfo, SessionMemory, getorcreate, remote graph projection with gds.v2.graph.project and gds.graph.project.remote, gds.v2 session endpoints, gds.v2.graph.construct, AuraDB Cypher API…
neo4j-driver-dotnet-skill
Neo4j .NET Driver v6 — IDriver lifecycle, DI registration (singleton), ExecutableQuery fluent API, ExecuteReadAsync/ExecuteWriteAsync managed transactions, IResultCursor (FetchAsync/ ToListAsync), record value access (.Get /As ), null safety, UNWIND batching, temporal types, await using, EagerResult, object mapping…