agoragentic-integrate
Skill41 starsChanged 44 days agoMITView on GitHub
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.
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Prefer thin adapters over forks or duplicate runtimes.
- Distinctive: line 15
Keep local integration separate from hosted activation, marketplace publication, payment enablement, or trust mutation.
- Distinctive: line 16
Add deterministic fixtures and one demonstrable user outcome before advertising support.
- Distinctive: line 23
Read its qualification record before claiming support: SDK control-wire tests with synthetic CLI peers do not establish real CLI …
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agoragentic Integrate
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
Other versions1 project uses a version of this.
Word for word · 1
- rhein1/agoragentic-integrations★ 41100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository36 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/agoragentic-assure.mdcCursor rule
- .cursor/rules/agoragentic-deploy.mdcCursor rule
- .cursor/rules/agoragentic-execute.mdcCursor rule
- .cursor/rules/agoragentic-govern.mdcCursor rule
- .cursor/rules/agoragentic-integrate.mdcCursor rule
- .cursor/rules/agoragentic.mdcCursor rule
- .cursor/rules/agoragentic-prove.mdcCursor rule
- .cursor/rules/agoragentic-sell.mdcCursor rule
- .cursor/rules/agoragentic-use.mdcCursor rule
- llms-full.txtllms.txt
- llms.txtllms.txt
- agent-payments-assurance-challengeSkill
- agoragentic-assureSkill
- agoragentic-deploySkill
- agoragentic-executeSkill
- agoragentic-governSkill
- agoragentic-proveSkill
- agoragentic-sellSkill
- agoragenticSkill
- agoragentic-useSkill
- integration-qualificationSkill
- agoragentic-prime-agentSkill
- agoragenticSkill
- agoragentic-assureSkill
- agoragentic-deploySkill
- agoragentic-executeSkill
- agoragentic-governSkill
- agoragentic-integrateSkill
- agoragentic-proveSkill
- agoragentic-sellSkill
- agoragenticSkill
- agoragentic-useSkill
- agoragentic-transaction-assuranceSkill
- agoragentic-transaction-assurance-evalSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.