Mmcp.market

tdm-daos-agent skill

by ToDealMarket·ToDealMarket/tdm-daos-agent·9 stars·MIT

Handle the current public TDM DaOS payment contract and recovery guidance. Use when a TDM service returns HTTP 402 from POST /authorize, when the user needs help with Session Gas Tank behavior, or when the user should be guided toward tdm connect, tdm fuel, tdm sweep, or tdm cashout.

A100/100content scan

Is the tdm-daos-agent skill safe?

Clean: nothing in its files matched our rules. We read 3 files in the folder on 2026-09-28.

No findings.

Install the tdm-daos-agent skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/ToDealMarket/tdm-daos-agent.git /tmp/tdm-daos-agent
mkdir -p ~/.claude/skills
cp -r /tmp/tdm-daos-agent/. ~/.claude/skills/tdm-daos-agent
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

TDM DaOS Agent

TDM DaOS Agent is the agent guidance layer inside TDM DaOS. Treat the TDM SDK npm package and Contour Runtime as the canonical product surface; this skill only explains agent-facing payment interpretation, recovery, and safe next actions.

Use this skill for

  • HTTP 402 responses from POST /authorize
  • billingMode, settlementMode, paymentOptions, and retryEndpoint
  • current JS helper names such as makePayable(...), createFetchHookClient(...), createAuthorizeClient(...), createGatewayClients(...), createSessionTanksClient(...), and createCheckoutClient(...)
  • framework-mode charge helpers: charge(...), chargeFetchHandler(...), chargeExpressHandler(...), chargeHonoHandler(...), chargeNextHandler(...), chargeElysiaHandler(...), chargeDenoHandler(...)
  • session recovery using tdmgetsession_state
  • runtime discovery using tdmcapabilitylist
  • plugin, contour, budget, and gated memory guidance through current MCP tools
  • sessiongastank guidance
  • sweep vs cashout clarification
  • agent vault command guidance
  • agent-first paid execution guidance for tools, APIs, routes, and runtime actions

Read only what you need

  • Read references/adaptation-map.md for older terminology and draft wording.
  • Read references/authorize-contract.md for current public fields and endpoints.
  • Read references/mcp-runtime.md for state-based recovery guidance.
  • Read references/sdk-sweep-capabilities.md before suggesting sweep flows.
  • Read references/vault-scenarios.md for agent vault and cashout guidance.

Hard rules

  1. Do not invent undocumented payment fields.
  2. Prefer exact current fields: allowed, authorizationId, charged, balanceMinor, priceMinor, billingMode, settlementMode, paymentOptions, and retryEndpoint.
  3. Use tdmcapabilitylist to discover the MCP surface when available.
  4. Use tdmgetsession_state before asking the user for money.
  5. If the state is UNINITIALIZED, instruct the user to run tdm connect.
  6. If the state is DEPLETED and dust is available, prefer tdm sweep.
  7. If the state is DEPLETED and no dust is available, suggest tdm fuel.
  8. Do not describe tdm sweep as a cashout.
  9. Do not suggest tdm cashout as a way to satisfy an active payment challenge.

Recommended operator commands

  • tdm vault create [--use]
  • tdm vault use
  • tdm connect
  • tdm login --gateway https://tdm.todealmarket.com (advanced/manual only)
  • tdm fuel --amount --yes
  • tdm sweep --network solana --resume-burner --deposit-address
  • tdm sweep --network solana --resume-burner --target-agent
  • tdm sweep --network base --project-id --treasury
  • tdm sweep status
  • tdm cashout
  • tdm agent list
  • tdm agent boot

Named vault guidance

  • Prefer one named vault per business contour when operators manage many agents.
  • For larger fleets, prefer multiple named vaults over one giant vault.
  • If the operator uses named vaults, respect their active vault or explicit --vault choice.

Product framing guidance

  • Treat TDM as DaOS-first: Contour Runtime + TDM Hub + AgentPay/Gateway.
  • Treat AgentPay as guidance inside DaOS, not as the whole product.
  • Default mental model: price a protected call, authorize it, then continue execution.
  • Mention file, note, or content unlock flows only as an additional layer on top of the core agent/runtime payment surface.

Bundled helpers

  • scripts/fetchx402price.mjs
  • scripts/runtdmsweep.mjs

All agent skills → · MCP servers