Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add tuantqse90/moltnode-mcp --skill chordgit clone --depth 1 https://github.com/tuantqse90/moltnode-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/tuantqse90/moltnode-mcp/chord)<a href="https://agentmods.dev/skills/tuantqse90/moltnode-mcp/chord"><img src="https://agentmods.dev/badge/skills/tuantqse90/moltnode-mcp/chord/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/tuantqse90/moltnode-mcp/chord"><img src="https://agentmods.dev/badge/skills/tuantqse90/moltnode-mcp/chord.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00247 | $0.05027 |
| Opus 5.5 | $0.00099 | $0.02011 |
| Sonnet 5.5 | $0.00049 | $0.01005 |
| Haiku 4.5 | $0.00025 | $0.00503 |
Grade A, and why
chord scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
compatibility: Needs HTTPS access to api.getchord.xyz with curl or python3. No key (60 requests a minute). How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chord
Chord indexes every DEX swap on eight EVM chains from its own tape, prices tokens from those trades, and routes a swap across every venue on a chain through one router contract. With this skill you read that data and prepare swaps carefully. You never sign, never broadcast, never hold funds.
- API:
https://api.getchord.xyz(REST, JSON; every path below starts with/v1). Reference: https://getchord.xyz/docs , OpenAPI https://getchord.xyz/docs/openapi.json , docs as MCP (Streamable HTTP) https://getchord.xyz/docs/mcp - Auth: none (60 requests a minute per IP). No key, no configuration.
- Helper:
python3 scripts/chord.py(path relative to this skill's folder, standard library only):token,price,board(these three also takesolana),stock,meta-quote,meta-swap,quote,swap-tx,simulate,get. It resolves symbols to addresses, converts amounts exactly, prints compact JSON, and builds an unsigned transaction only behind--user-confirmed. Prefer it; plaincurlworks too. Always passlimiton list calls and never cut JSON withhead -c(a truncated answer is a wrong answer). - If
chord_*MCP tools are in your tool list (the hosted server athttps://api.getchord.xyz/v1/mcp) they wrap the same API with the chain as a parameter:chord_chainssays what each chain supports,chord_quoteandchord_swap_txgo through the meta aggregator on every EVM chain, the rest are reads, pluschord_ask. Every rule below applies to them.
Chains
| Chain | id | key | Gas | Main stables and anchors | Data family |
|---|---|---|---|---|---|
| Monad | 143 | monad |
MON | USDC, AUSD, USDT0, WMON | /v1/tokens/market?chain=143 |
| Robinhood Chain | 4663 | robinhood |
ETH | USDG, WETH, 83 stock tokens | /v1/rh/* |
| Arc | 5042 | arc |
USDC | USDC (ERC-20 predeploy 0x3600...0000, 6 decimals), EURC |
/v1/arc/* |
| Avalanche | 43114 | avalanche |
AVAX | USDC, USDC.e (bridged), USDt, WAVAX | /v1/chains/avalanche/* |
| Base | 8453 | base |
ETH | USDC, USDbC (bridged), WETH | /v1/chains/base/* |
| BNB Chain | 56 | bnb |
BNB | USDT and USDC (both 18 decimals here), WBNB | /v1/chains/bnb/* |
| Arbitrum One | 42161 | arbitrum |
ETH | USDC, USDT0, USDC.e (bridged), WETH | /v1/chains/arbitrum/* |
| Ethereum | 1 | ethereum |
ETH | USDC, USDT (approve 0 first when an old allowance is left), DAI (18 decimals), WETH | /v1/chains/ethereum/* |
| Solana | none | solana |
SOL | USDC, USDT, wSOL (base58 mints, case-sensitive) | /v1/chains/solana/* (data) · /v1/sol/trade/* (swaps, beta) |
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 223 lines · 247 tokens per session scan A 34baea7a685f
chord is a skill published in the GitHub repository tuantqse90/moltnode-mcp (1 stars, last pushed 7d ago), licensed MIT. It adds 247 tokens to every session and 5,027 once invoked, about $0.0010 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-16.
Other skills, from other repositories
analyzing-ethereum-smart-contract-vulnerabilities
Perform static and symbolic analysis of Solidity smart contracts using Slither and Mythril to detect reentrancy, integer overflow, access control, and other vulnerability classes before deployment to Ethereum mainnet.
analyzing-ethereum-smart-contract-vulnerabilities
Perform static and symbolic analysis of Solidity smart contracts using Slither and Mythril to detect reentrancy, integer overflow, access control, and other vulnerability classes before deployment to Ethereum mainnet.
foundry-testing
Write and debug Foundry tests and Solidity scripts. Use when writing unit, fuzz, fork, or invariant tests, writing bulloak BTT .tree specs (Branching Tree Technique), using cheatcodes, benchmarking gas, measuring coverage, writing deploy scripts, or working in tests/ or script/.
solidity-coding
Write and modify production Solidity contracts in Foundry projects. Use when writing a contract, implementing a function, adding errors, events, or structs, designing contract architecture, optimizing gas, hardening security, planning upgrades, or working in src/.
alchemy-agentic-gateway
Use when accessing Alchemy APIs for RPC calls, token balances, NFT metadata, asset transfers, transaction simulation, or Alchemy-specific features. Also use when the user mentions "SIWE", "SIWS", "x402", "MPP", "mppx", or "agentic gateway" — this skill covers wallet-based auth flows for Alchemy's x402 and MPP…
alchemy-api
Integrates Alchemy blockchain APIs using an API key. Requires $ALCHEMYAPIKEY to be set; if unavailable, use the alchemy-agentic-gateway skill instead. Use when user asks about EVM JSON-RPC calls, token balances, NFT ownership or metadata, transfer history, token prices, portfolio data, transaction simulation…