Self Funding SetupSAFE

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

npx skills add https://github.com/wpank/Agentic-Uniswap/tree/main/.ai/skills/self-funding-setup

npx clawhub@latest install self-funding-setup

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: self-funding-setup
description: >-
  Set up a complete self-funding agent lifecycle in one command. Orchestrates
  5 agents to take an agent from zero to self-sustaining: provisions wallet,
  optionally deploys token with V4 pool, configures treasury management,
  registers identity on ERC-8004, and sets up x402 micropayments. Use when
  user wants to make their agent self-funding, earn and manage its own
  revenue, or configure autonomous agent operations end-to-end.
model: opus
allowed-tools:
  - Task(subagent_type:wallet-provisioner)
  - Task(subagent_type:token-deployer)
  - Task(subagent_type:treasury-manager)
  - Task(subagent_type:identity-verifier)
  - Read
  - Write
  - Edit
  - Glob
  - Grep
  - mcp__uniswap__get_supported_chains
  - mcp__uniswap__get_agent_balance
  - mcp__uniswap__check_safety_status
---

# Self-Funding Setup

## Overview

The most complex composite skill in the system. Orchestrates 5 specialized agents in sequence to take an agent from zero infrastructure to a fully self-sustaining economic entity -- wallet, optional token, treasury management, on-chain identity, and payment acceptance -- in a single command.

**Why this is 10x better than setting up each component manually:**

1. **5 domains compressed into 1 command**: Wallet provisioning, token deployment, treasury management, identity registration, and payment configuration each require different expertise and tooling. Manually coordinating these takes hours and requires deep knowledge of Privy/Turnkey APIs, Uniswap V4 pool creation, DCA strategies, ERC-8004 registries, and x402 protocol. This skill handles all five.
2. **Context flows between stages**: Each agent receives the output of all prior agents. The treasury-manager knows the wallet address from Step 1 and the token address from Step 2. The identity-verifier registers the wallet from Step 1 with the capabilities demonstrated by Steps 2-3. Without this skill, you'd manually copy-paste addresses and configuration between five separate tools.
3. **Conditional pipeline**: Token deployment (Step 2) is optional -- skip it for agents that earn through services rather than token economics. The skill adapts the remaining steps based on which revenue model is selected.
4. **Rollback awareness**: If Step 3 fails, Steps 1 and 2 are still valid and preserved. The skill reports exactly which steps succeeded and which failed, so you can fix the issue and re-run from the failure point rather than starting over.
5. **Progressive output**: You see each stage complete in real-time with a running summary. By the end, you have a complete "agent identity card" showing every component of the self-funding infrastructure.

## When to Use

Activate when the user says anything like:

- "Set up my agent to be self-funding"
- "Make my agent earn and manage its own revenue"
- "Configure autonomous agent operations end-to-end"
- "I want my agent to be self-sustaining"
- "Set up the full agent economy stack"
- "Bootstrap my agent's financial infrastructure"
- "Create a self-funding agent from scratch"
- "Full agent setup: wallet, token, treasury, identity, payments"

**Do NOT use** when the user only wants one component (use the individual skills: `setup-agent-wallet`, `deploy-agent-token`, `manage-treasury`, `verify-agent`, or `configure-x402` respectively), or when the agent is already partially set up and only needs one missing piece.

## Parameters

| Parameter        | Required | Default | How to Extract                                                          |
| ---------------- | -------- | ------- | ----------------------------------------------------------------------- |
| walletProvider   | No       | privy   | "privy" (dev), "turnkey" (production), or "safe" (max security)         |
| deployToken      | No       | false   | Whether to deploy an agent token: "yes", "with token", "launch token"   |
| tokenName        | If token | --      | Token name if deploying: "AgentCoin", "MyBot Token"                     |
| tokenSymbol      | If token | --      | Token symbol if deploying: "AGENT", "BOT"                               |
| chains           | No       | base    | Operating chains: "base", "ethereum", "base,ethereum"                   |
| revenueModel     | No       | x402    | "x402" (micropayments), "token-fees" (swap fees), "lp-fees", or "all"  |
| environment      | No       | dev     | "dev" (development), "staging", or "production"                         |
| initialFunding   | No       | --      | Initial funding amount: "$100", "0.1 ETH"                              |

If the user says "with token" or "launch a token", set `deployToken=true` and ask for `tokenName` and `tokenSymbol` if not provided.

## Workflow

```
                     SELF-FUNDING SETUP PIPELINE
  ┌──────────────────────────────────────────────────────────────────────┐
  │                                                                      │
  │  Step 1: WALLET PROVISIONING (wallet-provisioner)                    │
  │  ├── Determine provider: privy (dev) / turnkey (prod) / safe (max)   │
  │  ├── Provision wallet with signing capabilities                      │
  │  ├── Configure spending policies                                     │
  │  ├── Fund with gas (2x estimated need)                               │
  │  └── Output: Wallet address, provider, policies                      │
  │          │                                                           │
  │          ▼ wallet address feeds into all subsequent steps             │
  │                                                                      │
  │  Step 2: TOKEN DEPLOYMENT (token-deployer) [OPTIONAL]                │
  │  ├── Deploy ERC-20 token contract                                    │
  │  ├── Create Uniswap V4 pool with anti-snipe hooks                   │
  │  ├── Bootstrap initial liquidity                                     │
  │  ├── Lock LP tokens (10 years default)                               │
  │ 

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

What the source does

Filesystem

none-observed

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (1)

<key>k5Ey9KFlkqpj+SDkUw+5ED9lTA3En/qUi0zdrydUCH3kMWTE3Eh65NXnFCaxlY2omY2JHnlEoK7Li7oOEvM7eG5VPdcO/sFlMfoCRdnLYdepJ+uLzYwOWR8W4yQVve/clxVFTVRL4DFleKInGdpAxIbHZT2yi4ADAMENls1N1XSLojRuqXePXDeAT/4Mv4TTx0s

Gates applied: no_behavioural_pass.