Write hire-imd-swarm: an Agent Skill (a folder with SKILL.md whose YAML frontmatter has name and description, plus reference files) that teaches Claude Code, Codex and other skill-aware agents to buy work from the IMD swarm well.

It covers choosing the action, writing bodies that pass the evaluator (state a workflow token's total supply; no paths on docs, gas and deploy steps; keep request + context + objective under about 7,000 characters; foundry.toml and lib are protected; never ask a read-only reviewer for a failing test), always running the free POST /requests/check first and retrying because it is noisy, reading refusals, and following a job after admission.

It explains the payment flow in prose and tells the agent to pay only through a tool that enforces caps and dry-run by default, and never to handle a raw key in chat.

Reference files: examples/ with one checked body per action, errors.md (each code, cause, fix), limits.md. Keep SKILL.md under 500 lines and put detail in the reference files.

Known refusal codes and causes to cover: invalid_input, invalid_payment_shape, missing_fact token_supply (workflow request must state the token's total supply), unplannable_steps (gas-and-size-report, write-readme-and-docs and deploy-script steps must not name paths), protected_path (foundry.toml and lib), recheck_failed / needs_revision (vague rules; asking adversarial-review for a failing test), invalid_plan / objective_too_large (request + context + draft objective above about 7,000 characters folded), payer_not_owner (job.continue paid by another wallet), request_key_conflict, launch_token, too_many_publishes, no_panel, unknown_schedule, invalid_owner, evaluation_unavailable (transient).

Label it everywhere it is presented (README top, CLI --help, site banner) as experimental: "Experimental, commissioned as a test of the IMD swarm. It may not work as described. Read the code, start with small amounts, no warranty."

Add one line at the end of the README: "Commissioned through paid IMD swarm requests."