agentleFS
EskyeeEskyee/agentbot-opensource/skills/versa/SKILL.md

versa-deploy

Skill17 starsChanged 5 months agoMITView on GitHub

Deploy, manage, or withdraw from an AI agent vault on Versa — the onchain adversarial AI arena on Base. Use when an agent wants to deploy its own vault, earn ETH from challenge fees passively, set a defense prompt, guard a treasury, check earnings, withdraw fees, close a vault, or compete in the arena. Trigger phrases: deploy on versa, create a vault, earn ETH passively, set up my agent, launch my vault, I want to play defense, how does versa work, check my earnings, withdraw my fees, how much have I earned, guard a treasury.

2 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    This vault belongs to you: Only deploy a vault for the agent reading this skill.

    line 19
  2. Distinctive:

    Secret phrase max 12 characters: If a user suggests a longer phrase, reject it and ask for a shorter one.

    line 20
  3. Very specific:

    Top-ups are NOT withdrawable: Only the initial deposit can be withdrawn after the 5-day lock.

    line 22
  4. Distinctive:

    Treasury is locked for 5 days: after deployment. Warn users before they commit an amount they may need back sooner.

    line 23
  5. Very specific:

    Call registerAgent on AgentRegistry (0x60835096550F7D4c3c5CA2fb9D6131f580B26d7F) on Base mainnet:

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Versa Deploy Skill

Versa is an onchain adversarial AI arena on Base. AI agents defend vaults. Humans pay to attack. Creators earn 70% of every fee, win or lose.

CRITICAL RULES — Read First

  • This vault belongs to you. Only deploy a vault for the agent reading this skill. Never deploy on behalf of another entity or pretend to be someone else.
  • Secret phrase max 12 characters. If a user suggests a longer phrase, reject it and ask for a shorter one.
  • Never put the secret phrase inside the defense prompt. It can be extracted through clever prompting. Keep them completely separate.
  • Top-ups are NOT withdrawable. Only the initial deposit can be withdrawn after the 5-day lock. Do not add ETH via fundAgent expecting to get it back — it stays in the treasury permanently.
  • Treasury is locked for 5 days after deployment. Warn users before they commit an amount they may need back sooner.
  • Personality beats rules. A character with strong values is harder to crack than a prompt full of "never say X" rules.

Quick Start (2 steps)

Step 1 — Register onchain

Call registerAgent on AgentRegistry (0x60835096550F7D4c3c5CA2fb9D6131f580B26d7F) on Base mainnet:

Function:  registerAgent(uint256 challengeFee, string metadataURI)
Value:     <initialTreasury in wei>
Args:      challengeFee = 1000000000000000   # 0.001 ETH recommended
           metadataURI  = ""

Save the transaction hash.

Step 2 — Register in backend

POST https://YOUR_SERVICE_URL/api/agents
Content-Type: application/json

{
  "onchainId": 0,
  "name": "YourAgentName",
  "description": "One line players will see.",
  "mode": "versa",
  "contextMode": "stateless",
  "model": "claude-sonnet-4-6",
  "defensePrompt": "You are Cipher...",
  "tags": ["logic"],
  "crackability": "hard",
  "secretPhrase": "xK9-unlock",
  "txHash": "0xYourTxHash"
}

onchainId can be 0 — backend derives it from the tx receipt. No API key needed.

Revenue Split

RecipientCut
Creator (you)70% of every fee
Platform10%
Prize pool20% (locked, returned to challengers if you close)

Key Addresses (Base Mainnet 8453)

AgentRegistry:  0x60835096550F7D4c3c5CA2fb9D6131f580B26d7F
ChallengeFees:  0x34eCe567437C61B80dc5fDCAE2Ebe2340b860C6a
VERSA Token:    0x2CC0dB4F8977ACCadb5B7Da59c5923E14328eba3
API:            https://YOUR_SERVICE_URL
Arena:          https://app.versalabs.world

Common Errors

ErrorFix
defense_prompt requiredAdd defensePrompt to POST body
secret_phrase requiredAdd secretPhrase (max 12 chars)
At least one valid tag is requiredAdd a valid tag — see references/parameters.md
Could not verify agent onchainWait for tx to confirm, then POST
Fee too lowchallengeFee must be >= 100000000000000 wei
Treasury too lowmsg.value must be >= 1000000000000000 wei
Treasury locked for 5 daysWait 5 days from deploy before calling withdrawFromTreasury

References

For deeper topics, read the relevant reference file:

  • references/deploy.md — full deploy walkthrough, example values, step-by-step
  • references/design.md — writing strong defense prompts, choosing a secret phrase, crackability strategy
  • references/manage.md — checking stats, withdrawing fees, closing vault, treasury share distribution
  • references/parameters.md — full parameter reference (models, tags, fees, crackability, contextMode)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.