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 ruvnet/metaharness --skill oia-manifestgit clone --depth 1 https://github.com/ruvnet/metaharnessWrote 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/ruvnet/metaharness/oia-manifest)<a href="https://agentmods.dev/skills/ruvnet/metaharness/oia-manifest"><img src="https://agentmods.dev/badge/skills/ruvnet/metaharness/oia-manifest/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/ruvnet/metaharness/oia-manifest"><img src="https://agentmods.dev/badge/skills/ruvnet/metaharness/oia-manifest.svg" alt="Reviewed on agentmods" width="80" 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.00079 | $0.01024 |
| Opus 5 | $0.00039 | $0.00512 |
| Sonnet 5 | $0.00016 | $0.00205 |
| Haiku 4.5 | $0.00008 | $0.00102 |
Grade A, and why
oia-manifest 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 12d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
oia-manifest
Codex skill: emit/validate the OIA cross-cutting manifest layer (ADR-034, iter 121 → iter 122).
What it does
Emits .harness/oia-manifest.json — the harness's self-assessment against
the Open Intelligence Architecture (OIA) v0.1 9-layer reference model
published by the Agentics Foundation at https://oia.agentics.org.
The manifest declares:
- 9 layer alignments — L1 physicalCompute → L9 humanAndBrowserInterface,
each
full/partial/none/not-applicable - 6 horizontal spans — security · observability · identity · governance ·
policyEnforcement · interoperability, each
full/partial/nonewith animplementationreference (file path or ADR number) - 4 adjacent standards —
mcp,a2a,acp,agentProtocolwith current mode + wiring notes discoveryEndpoint+registryUrl(bothnullat v0.1; OIA has no registry yet)
Why a manifest, not a host adapter?
OIA at v0.1 has no runtime and no wire protocol — it's a vendor-neutral vocabulary for assessing system alignment. The right plug-in shape is a static cross-cutting manifest (ADR-034 Decision: Option B). It plugs in ABOVE the host adapter contract and BELOW the MCP policy gate.
Usage from Codex
/oia-manifest path=./my-harness
/oia-manifest path=./my-harness check=true
/oia-manifest path=./my-harness dry-run=true
Equivalent CLI
harness oia-manifest ./my-harness # write .harness/oia-manifest.json
harness oia-manifest ./my-harness --check # validate existing manifest
harness oia-manifest ./my-harness --dry-run # stdout, no file write
harness oia-manifest ./my-harness --json # stdout JSON
Verdict + exit codes (--check)
| Verdict | Exit | Meaning |
|---|---|---|
PASS |
0 | manifest shape ok, oiaVersion echoed |
DRIFT |
1 | shape mismatch — per-field reasons surfaced |
FAIL no manifest |
2 | .harness/oia-manifest.json missing |
Sample manifest (excerpt)
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.
- 12d ago First seen · 102 lines · 79 tokens per session scan A 30d751b7ca2b
oia-manifest is a skill published in the GitHub repository ruvnet/metaharness (645 stars, last pushed yesterday), licensed MIT. It adds 79 tokens to every session and 1,024 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
agent-agent
Agent skill for agent - invoke with $agent-agent.
agent-crdt-synchronizer
Agent skill for crdt-synchronizer - invoke with $agent-crdt-synchronizer.
agent-performance-benchmarker
Agent skill for performance-benchmarker - invoke with $agent-performance-benchmarker.
agent-quorum-manager
Agent skill for quorum-manager - invoke with $agent-quorum-manager.
agent-topology-optimizer
Agent skill for topology-optimizer - invoke with $agent-topology-optimizer.
agent-benchmark-suite
Agent skill for benchmark-suite - invoke with $agent-benchmark-suite.