Generate a read-only security report on threats involving MCP connections and operations. It groups findings by threat, reports the highest severity, and supports table or JSON output with a configurable severity threshold for failure.
Enterprise-review-grade threat model from `harness threat-model {path}`. Categorizes MCP-surface threats; emits `worst: 'clean'|'low'|'medium'|'high'` + per-threat findings. Pure-read.
Examines threats involving MCP connections and operations at a specified path and produces a categorized report. It lists findings for each threat and reports the highest severity across all findings. The four severity levels are clean, low, medium, and high. Output can be a table or JSON. You can also set a severity threshold so that findings at or above that level return exit code 1. The examination is read-only.
Use it to prepare material for an information security team during a security review before launch. It also helps with periodic audits when you want to check how threats involving MCP have changed. It complements harness-mcp-scan, which performs static checks for individual servers.
medium or higher.”Uses harness pinned to metaharness@~0.4.1, from a local installation or a dedicated cache. If harness cannot be found, it returns { degraded: true } instead of investigation results and exits with code 0.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 21, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
The companion to harness-mcp-scan for enterprise security reviews.
Where mcp-scan is a per-server static lint, threat-model produces a
categorized report suitable for sharing with an InfoSec team.
Implementation: scripts/threat-model.mjs.
harness binary (metaharness@~0.4.1, resolved from a
local install or the one-time ~/.ruflo/metaharness-cache-<pin> cache —
never @latest): harness threat-model <path> --json.{ worst, findings[] }.--fail-on <severity>: exit 1 when worst >= fail-on. Default high.| Severity | Rank |
|---|---|
| clean | 0 |
| low | 1 |
| medium | 2 |
| high | 3 |
oia-audit background
worker (ADR-150 Phase 2) to detect MCP-surface drift.Same pattern as the other skills: when harness is absent, emit
{ degraded: true } and exit 0. ADR-150 architectural constraint.
No 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.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.