Emit .harness/oia-manifest.json declaring layer alignment with the OIA v0.1 9-layer reference architecture. Self-describes the harness's MCP wiring, witness signing, audit log, identity posture (always 'none' at v0.1). --check verifies an existing manifest, --dry-run prints without writing, --json emits to stdout.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Codex skill: emit/validate the OIA cross-cutting manifest layer (ADR-034, iter 121 → iter 122).
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:
full / partial / none / not-applicablefull / partial / none
with an implementation reference (file path or ADR number)mcp, a2a, acp, agentProtocol with
current mode + wiring notesdiscoveryEndpoint + registryUrl (both null at v0.1; OIA has no
registry yet)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.
/oia-manifest path=./my-harness
/oia-manifest path=./my-harness check=true
/oia-manifest path=./my-harness dry-run=true
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 | 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 |
{
"schema": 1,
"oiaVersion": "0.1",
"harnessId": "my-bot@0.1.0",
"layerAlignment": {
"L4_toolsAndIntegrations": "full",
"L7_governanceAndPolicy": "full"
},
"horizontalSpans": {
"identity": { "status": "none", "implementation": null },
"security": { "status": "full", "implementation": "mcp-policy.json + ADR-022" }
},
"adjacentStandards": {
"mcp": { "mode": "local", "policyPath": ".harness/mcp-policy.json" }
},
"discoveryEndpoint": null,
"registryUrl": null
}
If a future OIA identity primitive ever wants to widen an MCP permission,
the composition is denied at the policy gate. The mcp-policy.json
default-deny posture is not negotiable for external identity claims.
validate-harness (iter 22) — release-readiness umbrellathreat-model (iter 114) — MCP threat-model for PR/compliance reviewdiag-harness (iter 70) — kernel-version skew checkNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.
The English summary is being prepared. Showing the original description.
Scaffold your own focused AI agent harness — pick host (Claude Code, Codex, pi.dev, Hermes), template, agents, skills, and ship a npm-publishable harness with its own npx CLI. Use when a user asks to "create my own agent harness", "scaffold a harness", "make a custom Claude Code plugin like ruflo", or "build a vertical AI assistant for X".
The English summary is being prepared. Showing the original description.
Kernel-version skew check (ADR-027). Reports manifest surface + manifest kernel + installed kernel + verdict (match/patch-diff/minor-diff/major-diff). Exits 1 on minor/major skew with a copy-pasteable `npm install @metaharness/kernel@X.Y.Z` next step. Exits 2 if no .harness/manifest.json at path.
The English summary is being prepared. Showing the original description.
Evolve this harness with Darwin Mode — frozen model, evolving harness (real, sandboxed, safety-gated).
The English summary is being prepared. Showing the original description.
Scaffold a ready-made AI agent harness in one command from the 19 published @metaharness/* example packages — 9 host integrations (Claude Code, Codex, Hermes, pi.dev, OpenClaw, RVM, Copilot, OpenCode, GitHub Actions) + 10 vertical pods (devops, research, trading, support, legal, coding, education, sales, gaming, repo-maintainer).
The English summary is being prepared. Showing the original description.
GCP Secret Manager integration: validate setup, fetch values, or confirm an NPM_TOKEN is non-revoked via `npm whoami`. Used for publish-time token rotation without long-lived keys in CI.
The English summary is being prepared. Showing the original description.