harness-oia-audit

Runs composite security audits combining threat modeling, MCP scanning, and architecture alignment checks.

70.1k|8.4k|Updated Jun 2, 2025
One-click install
npx skills add https://github.com/ruvnet/claude-flow --skill harness-oia-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-oia-audit
Source: https://github.com/ruvnet/claude-flow/tree/main/plugins/ruflo-metaharness/skills/harness-oia-audit
Command: npx skills add https://github.com/ruvnet/claude-flow --skill harness-oia-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security posture drift in agentic infrastructure is hard to detect when threat modeling, MCP server scanning, and architecture alignment checks run as separate, uncoordinated commands with no historical record. This Skill bundles all three MetaHarness static surfaces into one timestamped audit record so drift over time becomes visible and schedulable.

Core Features & Use Cases

  • Composite Audit Execution: Runs oia-manifest (L1-L9 layer alignment), threat-model (categorized MCP-surface threats), and mcp-scan (per-server policy and dependency findings) in a single pass.
  • Worst-Severity Aggregation: Computes a composite worst severity from the threat model and MCP scan findings, with an --alert-on-worst threshold that exits non-zero when breached.
  • Persistent Audit History: Stores each run in the metaharness-audit memory namespace under an ISO-timestamped key, enabling diff-based drift detection between audits.
  • Graceful Degradation: Emits a standard degraded payload when MetaHarness components are unavailable, flagging partial results per component instead of failing.
  • Use Case: Wire it into a weekly GitHub Actions cron job that fails the build whenever any HIGH-severity finding appears, while logging lower-severity drift for later review.

Quick Start

Ask the agent to run a composite MetaHarness audit on the current repository with an alert threshold of high severity and persist the result to the audit memory namespace.

Frequently Asked Questions about harness-oia-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a composite security audit on an MCP-based agent project?

Run the oia-audit.mjs script with a target path, which executes oia-manifest, threat-model, and mcp-scan in one pass. The composite worst severity is computed automatically and the record is persisted to the metaharness-audit memory namespace.

How to detect security drift over time in agentic infrastructure?

Schedule the audit via cron and retrieve past records from the metaharness-audit namespace using the memory list and retrieve commands. Compare composite.worst and component-level fields between two timestamped audits to identify drift.

Can I fail a CI job when a high-severity threat is found?

Yes, pass --alert-on-worst high to make the script exit with code 1 when the composite worst severity meets or exceeds the threshold. Lower-severity findings are logged in the audit record without blocking the pipeline.

What happens if MetaHarness components are unavailable during an audit?

When all three components report metaharness-not-available, the script emits a standard degraded payload and exits 0. If only some components are degraded, each carries its own degraded flag while the audit still persists what it gathered.

What are the limitations of this composite audit approach?

The audit only covers static surfaces: architecture alignment, threat modeling, and MCP scanning. It does not perform runtime behavioral analysis, and its findings depend on the underlying MetaHarness components being installed and functional.