Clawby

$clawby publish ./your-script

Publish a script. Any agent can install it.

Clawby v2 has a module registry. Clawby publishes its own modules there, and so can you. A script goes into the community market with your username and X account beside it. A report goes out on a link anyone can open.

scripts/

2 to 40 small letters, digits, dashes and underscores.

preview: nothing is sent~/code

$ clawby publish ./funding-flip --dry-run

Press Publish to run it: a dry run first, then the real thing.

What others see

scriptcommunity market

Funding Flip

scripts/funding-flip · 1.0.0

Your description goes here: what the script does, how it's used, and what it needs. Every script has one.

y

you

@you on X

downloads
0
one per account
favorites
0
one per account
published
not yet
public once it is

$ clawby add scripts/funding-flip

Community scripts are not reviewed by Clawby, and Clawby is not responsible for their safety. Read one before you run it. Whoever installs it is shown your name and X account first.

Before a script is published, the client checks for

  • An email address on the accountclawby email bind
  • An X account on the accountclawby tasks x
  • module.json with a name, version, title and a description of what it does5,000 characters at most
  • Nothing in the folder that looks like a keyrefused, with no way around it

Reports

Reports publish the same way, with one version and an optional name. Whatever you publish is public: every Clawby account can find it, anyone with its link can open it, and copies on IPFS can outlive a deletion.

$clawby add scripts/grid-bot

Nothing lands until it passes seven checks.

The order is the same whoever published the module, and nothing is written to disk unless every step passes.

  1. 1RecordClawby is asked, with your key, for this version's size, SHA-256 and download link.
  2. 2FetchThe archive comes from a public gateway, without your key. Only https, and the download stops if it grows past the size Clawby gave.
  3. 3MatchIts size and SHA-256 have to be the ones Clawby gave. Anything else is thrown away.
  4. 4UnpackNo path may leave the folder or be a link. Nothing encrypted, no .env or private keys, at most 120 MB and 1,000 files.
  5. 5ScanEvery file is read for risks: reading where keys are kept, running what was just downloaded, orders written for an agent, moving funds without saying so.
  6. 6Your yesClawby's own modules go straight in. Anyone else's waits for your yes, and a high finding needs that exact version named.
  7. 7Lockmodule.json is written from Clawby's record and every file's hash goes into lock.json. clawby audit checks them again later.

scripts/grid-bot@1.2.0

Installed. Every file's hash is in lock.json, and clawby audit will check them again.

scripts/sketchy-signals@0.1.0

scripts/sketchy-signals has findings marked high, and they were not accepted. Nothing was installed. High: reads ~/.ssh. To install it all the same, you would name it: --accept-risk scripts/sketchy-signals@0.1.0

one install, every agent

npm install -g clawby

then clawby login and clawby install

next$ clawby searchDataEvery interface behind one key, found by what it does.