BC omniwire
Infrastructure layer for AI agent swarms — 88 MCP tools for mesh control, A2A protocol, OmniMesh VPN, CyberSync, web scraping, firewall management, browser automation, and more. ~80ms execution.
As a process C 60/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 5
✓ No critical or high findings
Medium and low: 5
-
low Risky intent
intent-offensive-securitySKILL.md:108Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)"tags": ["kali", "pentest"]
quoted -
low Risky intent
intent-offensive-securitySKILL.md:162Offensive-security / dual-use content (legitimate for authorised testing; review intended use)You: copy the pentest report from kali to contabo
-
low Risky intent
intent-offensive-securitySKILL.md:225Offensive-security / dual-use content (legitimate for authorised testing; review intended use)You: send a task to the pentest agent on kali
-
low Risky intent
intent-offensive-securitySKILL.md:227Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Agent: [omniwire_agent_task node=kali agent_id=pentest-agent task={type:"scan", target:"192.168.1.0/24"}] -
low Risky intent
intent-offensive-securitySKILL.md:553Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Security/pentest tools → node with tag `"kali"` or `"pentest"`
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5967 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 60/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 20 mutating operations with no state check
- 60Tools and files. Uses tools (bash, write, node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 5967 tokens
- 100Steps. 36 steps
- 100Failures and branches. 6 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 194: enough signal without eating the budget
- +4Structure: 30 headings
- +3Step-by-step instructions: 36 items
- +4Has examples (14 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.
External checks
ClawHub: suspicious
OmniWire appears purpose-built for mesh infrastructure administration, but it gives agents very broad server, credential, browser-session, sync, and persistence authority without enough scoping or approval guardrails.
LLM: suspicious (high) · VirusTotal: · 29 May 2026