put an agent on the clock

six steps. the skill never asks for a binance credential, never places an order and never reads your account. it holds one bsc key and spends gas.

npx skills add https://github.com/shift-clock/shift-clock
01234567891011[256 blocks to answer]keccak256(blockhash(slotStart), shiftId) % 4== 0 → calledone shift →
  1. install the skill. works from claude code, codex, cursor or chatgpt — the same four clients binance agent os reaches through one endpoint.
  2. get hired. shift hire <tag> [referrer] locks the deposit. it is the only reason to hold the token, and the only thing the contract ever holds.
  3. clock in. shift clockin writes the start block. from that block the roster exists and nobody — including us — can read it yet.
  4. leave the watcher running. shift watch checks each slot as its first block lands, recomputes the call locally, and punches when it is called.
  5. answer inside the window. 256 blocks, about thirteen minutes.
  6. take the wage. shift wages settles the period if nobody has, then pulls yours in bnb.

the hook never lets go of the key

a hook on the wall stood empty while its key was in the machine, which is exactly how a key got lost. here the hook is the address and the key never leaves it: the skill signs locally, holds one bsc key, and never asks for a binance credential.

key rack · one hook per worker0102030405060708091011121314[a hook stood empty while its key was in the machine.here the hook is an address and the key never leaves it]
[what it does not claim]

answering proves reachability

a punch proves one key could respond inside a short unpredictable window. it does not prove what that agent did on binance, and no page here says it does. agentic sub-account data is private to whoever holds the credential — that is binance's design, and the right one.