SUIBROKERS DAO · field note
AGENTS.md for crypto work: network, budgets, and instructions
A practical guide to writing agent instructions that make network, asset, budget, authorization, and evidence expectations explicit.
The SUIBROKERS AGENTS.md is a user-facing instruction file for an AI host, separate from a repository maintainer’s AGENTS.md. Its job is to make a participant’s boundaries explicit: use Sui mainnet, respect asset and budget limits, ask before actions, and report Points from the ledger rather than from a model’s guess.
What the template should say
A useful template can be short and operational:
# SUIBROKERS participant rules
- Use Sui mainnet only unless I explicitly name another network.
- Treat asset identity, wallet address, amount, and app URL as review fields.
- Never connect, sign, submit, or retry a wallet action without my explicit confirmation.
- Respect the budget and asset limits I state in this session.
- Use MCP for status, history, season, Desk, Partner, and preparation only.
- Review quotes and transaction details in the SUIBROKERS app.
- Report confirmed ledger records separately from previews, estimates, pending rows, and failures.
- Never claim Points, Trust, or NFT qualification from text generation alone.
The packaged template provides these boundaries and can be merged into a participant project after review. A local file does not grant the model a wallet or make a host compatible with the SUIBROKERS MCP. Hosted ChatGPT Work has its own plugin and remote-MCP path; it should not be described as automatically reading a local Codex config or local AGENTS.md.
Turn an instruction into a reviewable action
Ask the host for preparation, not execution:
Read the SUIBROKERS status and prepare a Swap checklist for the selected Sui wallet. Return the app URL, asset, amount, current status, and review questions. Stop before quote, build, signing, or sending.
Before a user signs, check network, wallet, asset identity, amount, output, fee, gas, minimum received, and slippage. For The Desk, check whether the requested action is a deposit or withdrawal. For Partners, check the first-valid-referral path and invited wallet connection.
Report ledger facts
The template should force exact fields into the answer: transaction digest when present, confirmation state, verification state, source record, Points value, season stage, threshold, capacity, and allocation state. If a field is unavailable, say unavailable. Do not turn an entry Desk Points estimate into a credit or a season threshold into an NFT promise.
The current Swap rule is 1 Point per $4 of verified volume. Partner Points, Trust, and accrued revenue use separate rules. The planned token and NFT Vault remain separate, while current Swap and The Desk remain usable without holding the token.
Kit references
Use the user-facing AGENTS.md template with the participant kit README; these are user instructions, not repository maintainer guidance.
Sources
An AGENTS.md file can make network, budget, confirmation, and evidence rules durable, but it cannot approve a transaction or make a host compatible. Keep those instructions explicit, then validate the actual tool and wallet state at the point of action.