Skip to content
Back to skills

Agoragentic Integrate

ASecurity

Connect an external agent host, framework, tool, or specialist engine to Agoragentic governance and receipts. Use for adapters, lifecycle mapping, MCP/tool discovery, and bounded integration design.

  • 40 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added August 31, 2026
ai-agentsrustgogitsecurity

Works with

  • cli
  • mcp

Security analysis

A100/100

Scanned September 21, 2026

npx -y skills add rhein1/agoragentic-integrations --skill agoragentic-integrate --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agoragentic Integrate?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Agoragentic Integrate
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rhein1-agoragentic-integrate/badge)](https://www.skillsdirectory.com/skills/rhein1-agoragentic-integrate)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: agoragentic-integrate
description: Connect an external agent host, framework, tool, or specialist engine to Agoragentic governance and receipts. Use for adapters, lifecycle mapping, MCP/tool discovery, and bounded integration design.
---

# Agoragentic Integrate

Prefer thin adapters over forks or duplicate runtimes.

For each external system:
1. Identify native lifecycle/tool hooks and execution boundaries.
2. Map them into existing Harness Core middleware events.
3. Reuse existing policy and receipt schemas rather than duplicating them.
4. Store hashes, bounded summaries, status, and evidence refs instead of raw private outputs by default.
5. Keep local integration separate from hosted activation, marketplace publication, payment enablement, or trust mutation.
6. Add deterministic fixtures and one demonstrable user outcome before advertising support.

Useful integration targets include coding-agent hosts, web/data engines, quality/security scanners, optimization systems, and rendering engines.

For Anthropic Commerce Agents, use the existing `claude-agent-sdk/commerce/`
title-edit fixture and its pinned shared-executor conformance path. Keep host
approval outside model tools and revalidate the exact change at apply time.
Read its qualification record before claiming support: SDK control-wire tests
with synthetic CLI peers do not establish real CLI enforcement or model-runtime
compatibility. Never repoint the synthetic store at a live merchant.

## Advanced Context

- Commerce fixture and qualification: <https://github.com/rhein1/agoragentic-integrations/tree/main/claude-agent-sdk/commerce>
- agent workflow contracts: <https://github.com/rhein1/agoragentic-integrations/blob/main/docs/agent-workflow-contracts.md>
- MCP adapter: <https://github.com/rhein1/agoragentic-integrations/tree/main/mcp>
- federation and interchange: <https://github.com/rhein1/agoragentic-integrations/tree/main/interchange>

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…