Instruction file imported from rhein1/agoragentic-integrations (.cursor/rules/agoragentic-integrate.mdc). Copyright stays with the author.

Agoragentic Integrate

Name: agoragentic-integrate
Author: rhein1

Prefer thin adapters over forks or duplicate runtimes.

For each external system:

Identify native lifecycle/tool hooks and execution boundaries.
Map them into existing Harness Core middleware events.
Reuse existing policy and receipt schemas rather than duplicating them.
Store hashes, bounded summaries, status, and evidence refs instead of raw private outputs by default.
Keep local integration separate from hosted activation, marketplace publication, payment enablement, or trust mutation.
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

{ "ocm": "1", "id": "rhein1-agoragentic-integrations-agoragentic-integrate-rule", "kind": "skill", "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.", "publisher": "rhein1", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github-cursor-rules" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "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." ], "primary": false, "metadata": { "source": { "provider": "github-cursor-rules", "repository": "https://github.com/rhein1/agoragentic-integrations", "path": ".cursor/rules/agoragentic-integrate.mdc", "ref": "6d59ab1d7c48e66be75efc36df8a0c84710175a2", "url": "https://github.com/rhein1/agoragentic-integrations/blob/6d59ab1d7c48e66be75efc36df8a0c84710175a2/.cursor/rules/agoragentic-integrate.mdc", "key": "rhein1/agoragentic-integrations/.cursor/rules/agoragentic-integrate.mdc" } }, "instructions": "# Agoragentic Integrate\n\nPrefer thin adapters over forks or duplicate runtimes.\n\nFor each external system:\n1. Identify native lifecycle/tool hooks and execution boundaries.\n2. Map them into existing Harness Core middleware events.\n3. Reuse existing policy and receipt schemas rather than duplicating them.\n4. Store hashes, bounded summaries, status, and evidence refs instead of raw private outputs by default.\n5. Keep local integration separate from hosted activation, marketplace publication, payment enablement, or trust mutation.\n6. Add deterministic fixtures and one demonstrable user outcome be", "cost": { "context_tokens": 422 } }

agoragentic-integrate

About

Agoragentic Integrate

Advanced Context

Use it

Manifest

Reviews