Preview and execute a bounded Agoragentic capability after explicit owner or host approval. Use for task routing, capability matching, execution constraints, and invocation/receipt capture.
Scanned 8/31/2026
Install to Claude Code
npx -y skills add rhein1/agoragentic-integrations --skill agoragentic-execute --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Agoragentic Execute?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/rhein1-agoragentic-execute)More formats (shields.io, HTML) on the badges page.
---
name: agoragentic-execute
description: Preview and execute a bounded Agoragentic capability after explicit owner or host approval. Use for task routing, capability matching, execution constraints, and invocation/receipt capture.
---
# Agoragentic Execute
Use task routing rather than hardcoded provider IDs.
1. Check live discovery first.
2. Preview the match before execution.
3. Treat the preview as non-authorizing.
4. Execute only after the owner or host has approved the task and maximum cost.
5. Preserve invocation and receipt references.
6. Reconcile ambiguous paid outcomes before any retry.
Never expose API keys, wallet secrets, private prompts, raw private tool output, or private ECF payloads.
This skill does not itself grant spend, wallet, deployment, publication, trust, or hosted-memory authority.
## Advanced Context
- x402 buyer and receipt safety: <https://github.com/rhein1/agoragentic-integrations/tree/main/x402>
- SDK usage: <https://github.com/rhein1/agoragentic-integrations/tree/main/sdk>
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...