vendor-adapters

Manage vendor-specific adapters and authentication modes within a provider harness.

Updated May 11, 2026
One-click install
npx skills add https://github.com/AesopScott/mojo --skill vendor-adapters
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vendor-adapters
Source: https://github.com/AesopScott/mojo/tree/main/harnesses/skills/vendor-adapters
Command: npx skills add https://github.com/AesopScott/mojo --skill vendor-adapters

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of uncontrolled expansion of provider capabilities, ensuring that new vendor integrations are strictly bounded by defined auth-modes and adapter configurations.

Core Features & Use Cases

  • Capability Control: Define specific adapter sets and auth-mode configurations for new providers.
  • Boundary Enforcement: Prevent accidental overreach by enforcing strict rules on what a provider can access or execute.
  • Use Case: When adding a new AI model provider, use this skill to define the exact transport rules and auth requirements, ensuring the integration remains within the established security boundary.

Quick Start

Use the vendor-adapters skill to inspect the current provider boundary and propose a configuration change for a new integration.

Frequently Asked Questions about vendor-adapters

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

FAQPage Schema
How do I secure external model provider integrations in a provider harness?

To secure external model provider integrations, you define specific adapter sets and auth-mode configurations within a provider harness. This enforces strict capability boundaries, preventing accidental overreach and ensuring controlled access to external providers.

What is the best way to enforce capability boundaries for new vendor adapters?

The best way to enforce capability boundaries for vendor adapters is by applying strict rules on transport and auth requirements. This prevents uncontrolled expansion of provider capabilities, ensuring new integrations remain within established security boundaries.

How do I configure auth-modes when adding a new AI model provider?

To configure auth-modes for a new AI model provider, you inspect the current provider boundary and propose a configuration change. This defines exact transport rules and authentication requirements to maintain a modular, testable integration.

When do I need strict capability boundaries for provider configuration management?

You need strict capability boundaries for provider configuration management when your software engineering workflows require controlled access to external model providers. This prevents uncontrolled expansion of provider capabilities and ensures secure vendor integrations.

Does this approach support modular and testable vendor adapter configurations?

Yes, managing vendor-specific adapters within a provider harness supports modular and testable configurations. It isolates authentication modes and transport rules, satisfying requirements for secure and strictly bounded provider integrations.