M

MetaMynd OpenShell Integration 

Proof of concept for MetaMynd authorization middleware in NVIDIA OpenShell, demo

metamynd/openshell-integration · unreleased source · c4426ee · Tools & Integrations

by MetamyndOwner verifiedScan grade: Acceptable

Metamynd authorization middleware for NVIDIA OpenShell . Every outbound purchase from a sandboxed agent is authorized against a live mandate, credential-swapped by OpenShell, re-verified by Metamynd's gateway, and executed exactly once.

Follow0
Protect this install with HOL Guard

Guard checks the skills and MCP servers a plugin adds on your machine and asks you before a risky action runs. The scores above are free, and no plan changes them.

Is NVIDIA OpenShell Integration With Metamynd a fit?

From the plugin's manifest and HOL's scan. Anything the plugin does not declare is shown as not declared.

Works with

Not declared

Before you install

Sign-in
Not declared
Declared access
Not declared
License
Not declared

Check before relying on it

  • No license declared in the manifest.

What is MetaMynd OpenShell Integration?

MetaMynd OpenShell Integration is a published tools & integrations plugin for AI coding agents, developed by Metamynd and distributed through the HOL AI plugin registry. Proof of concept for MetaMynd authorization middleware in NVIDIA OpenShell, demonstrated with a governed purchasing flow.

Canonical slug
metamynd/openshell-integration
Version
unreleased source · c4426ee · updated Nov 6, 2026

Registry snapshot

Owner verification
Verified on HOL as @metamyndai
Scanner
HOL plugin scanner
Security result
Needs review
Digest verified
Yes

Trust and security

Trust & reputation

On-Chain Verified
88

HOL Trust Score

Per-metric points (0–100 each) combined via a weighted average into the overall score.

Installability
100/100
Maintenance
100/100
MCP server setup
100/100
Plugin Security
78/100
Provenance
80/100
Publisher Quality
100/100

Provenance

Plugin root
.
Source repo
https://github.com/Metamynd/openshell-integration
Source commit
c4426ee5a015…
Publisher verified
Yes
Owner verified
@metamyndai
Agent Plugins 1.0
Not detected

README badge detected

The source repository README links to this HOL listing. Distribution, not security evidence. It adds a 2% engagement adjustment to the overall trust score and never changes the security result.

Needs review
Security result
78
Security score
0
High findings
Provider
codex-plugin-scanner
Grade
C · Acceptable
Version
3.24.2
cisco-skill-scanner: skippedcisco-mcp-scanner: skipped

Manifest Validation

21/31

9 checks

Security

16/16

9 checks

Operational Security

3/6

5 checks

Best Practices

6/9

5 checks

Marketplace

N/A

3 checks · not applicable

Skill Security

N/A

3 checks · not applicable

Code Quality

10/10

2 checks

Published advisories

None matched in GitHub security advisories, checked . This covers published advisories only, not problems nobody has reported.

GitHub security advisories are those the source repository has published.

Findings

lowoperational-securityDEPENDABOT_MISSING

Automation or dependency surfaces exist, but .github/dependabot.yml is missing.

Add Dependabot updates for GitHub Actions and dependency manifests.

infomanifest-validationPLUGIN_JSON_RECOMMENDED_AUTHOR

The manifest is missing the documented recommended field "author".

Add "author" to strengthen the plugin manifest metadata.

infomanifest-validationPLUGIN_JSON_RECOMMENDED_LICENSE

The manifest is missing the documented recommended field "license".

Add "license" to strengthen the plugin manifest metadata.

infomanifest-validationPLUGIN_JSON_RECOMMENDED_KEYWORDS

The manifest is missing the documented recommended field "keywords".

Add "keywords" to strengthen the plugin manifest metadata.

infomanifest-validationPLUGIN_JSON_INTERFACE_SHORTDESCRIPTION

The interface object is missing a valid "shortDescription" value.

Add a valid "shortDescription" field to the interface metadata.

infomanifest-validationPLUGIN_JSON_INTERFACE_LONGDESCRIPTION

The interface object is missing a valid "longDescription" value.

Add a valid "longDescription" field to the interface metadata.

infomanifest-validationPLUGIN_JSON_INTERFACE_CAPABILITIES

The interface object is missing a valid "capabilities" value.

Add a valid "capabilities" field to the interface metadata.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_WEBSITEURL

The interface field "websiteURL" must use HTTPS or point to a safe in-repo asset.

Update "websiteURL" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_PRIVACYPOLICYURL

The interface field "privacyPolicyURL" must use HTTPS or point to a safe in-repo asset.

Update "privacyPolicyURL" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_TERMSOFSERVICEURL

The interface field "termsOfServiceURL" must use HTTPS or point to a safe in-repo asset.

Update "termsOfServiceURL" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_COMPOSERICON

The interface field "composerIcon" must use HTTPS or point to a safe in-repo asset.

Update "composerIcon" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_LOGO

The interface field "logo" must use HTTPS or point to a safe in-repo asset.

Update "logo" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_SCREENSHOTS

The interface field "screenshots" must use HTTPS or point to a safe in-repo asset.

Update "screenshots" to use HTTPS or an existing relative asset path.

infobest-practicesCODEXIGNORE_MISSING

A .codexignore file helps prevent accidental inclusion of local artifacts and secrets.

Add a .codexignore file with generated assets, local state, and secret paths.

Install guidance

Install in Source

Install from a native release archive or the assessed source revision.

Install guide
  1. 1

    Download the release archive

    Use a published GitHub release archive. The catalog version is the package version at the assessed commit.

    shell
  2. 2

    Follow the publisher install guide

    https://github.com/Metamynd/openshell-integration/blob/c4426ee5a015cafca019744e2f09bb5ff136eb4d/docs/INSTALL.md

Did setup work in Source?

No setup reports for Source yet. Self-reported by signed-in visitors. Copying a command is not counted, and most installs are never reported.

Attested installs: Fewer than 10 attested installs of this plugin in week 2026-W44, so no number is shown. Counted from opt-in HOL Guard install reports, once per machine and runtime, and never mixed with the answers above. How install reports work.

1 / 1

MetaMynd OpenShell Integration demo video

Loading reviews

Plugin manifest

{
  "name": "openshell-integration",
  "version": "0.0.0",
  "description": "Proof of concept for MetaMynd authorization middleware in NVIDIA OpenShell, demonstrated with a governed purchasing flow",
  "repository": "https://github.com/Metamynd/openshell-integration",
  "homepage": "https://github.com/Metamynd/openshell-integration",
  "interface": {
    "displayName": "MetaMynd OpenShell Integration",
    "developerName": "Metamynd",
    "category": "Tools & Integrations"
  },
  "holManifestOrigin": "synthesized",
  "registryIndexVersion": 9
}

File inventory

.codex-plugin/plugin.json

plugin-manifest

496 bytes

1795f9ac5fa6e644…

eslint.config.js

file

305 bytes

e5c96882dc0b415a…

LICENSE

file

1,420 bytes

0cab1b96e10a2549…

package-lock.json

file

58,034 bytes

08328afb2aae25b9…

package.json

file

513 bytes

896f3f0610b4fab3…

README.md

file

3,613 bytes

70c13da09646bbdf…

README.md

file

3,613 bytes

70c13da09646bbdf…

SECURITY.md

file

670 bytes

bb1c50dad3f92506…

tsconfig.json

file

317 bytes

43db3e80611c04ba…

NVIDIA OpenShell Integration With Metamynd — Frequently asked questions

What is NVIDIA OpenShell Integration With Metamynd?
NVIDIA OpenShell Integration With Metamynd is an AI plugin in the HOL registry. Metamynd authorization middleware for NVIDIA OpenShell . Every outbound purchase from a sandboxed agent is authorized against a live mandate, credential-swapped by OpenShell, re-verified by Metamynd's gateway, and executed exactly once.
How do I install NVIDIA OpenShell Integration With Metamynd?
Install NVIDIA OpenShell Integration With Metamynd in your harness: Source — https://github.com/Metamynd/openshell-integration/releases. Full step-by-step guidance is on the HOL plugin page.
How do I install NVIDIA OpenShell Integration With Metamynd in Source?
To install NVIDIA OpenShell Integration With Metamynd in Source, start with https://github.com/Metamynd/openshell-integration/releases. The complete step-by-step install guide for Source is on the HOL plugin page.
Is NVIDIA OpenShell Integration With Metamynd free?
NVIDIA OpenShell Integration With Metamynd is listed as free on HOL.
How is the Trust Score for NVIDIA OpenShell Integration With Metamynd computed?
NVIDIA OpenShell Integration With Metamynd has a HOL Trust Score of 88 out of 100. The score is a weighted sum of six components from a static scan of the source, capped for high-severity findings and adjusted by two disclosed policies. Memberships and payments are not inputs, and a scan is not a safety guarantee. Full breakdown: https://hol.org/registry/plugins/metamynd%2Fopenshell-integration/trust
Who publishes NVIDIA OpenShell Integration With Metamynd?
NVIDIA OpenShell Integration With Metamynd is published by Metamynd and listed on HOL.
Is NVIDIA OpenShell Integration With Metamynd available now?
NVIDIA OpenShell Integration With Metamynd is currently available according to its latest public launch.

Directory acceptance

Listed in 0 of 5 directory lists

Read from the list each directory publishes on GitHub. Being listed means the directory accepted the plugin; it is not a HOL security rating.

Lists last read . HOL re-reads them every day.

Submitting it? Check it against each directory's rules

Install signal

HOL cannot see every install. These are separate signals from different sources, so they are not added together. Counts under each floor show as <N.

Install commands issued here
<5
HOL Guard install commands issued from this listing, last 28 days.
Opt-in install reports
<10
Machines that reported installing it through HOL Guard in week 2026-W44. Reporting is opt-in, so most installs are not counted.
HOL Guard workspaces
<5
Workspaces that approved it or include it in an approved-plugin feed, as of today.
New GitHub stars
<5
From HOL's GitHub snapshots of the repository, 2026-11-05 to 2026-11-06.

History, reviews, and similar plugins

Latest launch