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 moltnodegit 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/moltnode)<a href="https://agentmods.dev/skills/tuantqse90/moltnode-mcp/moltnode"><img src="https://agentmods.dev/badge/skills/tuantqse90/moltnode-mcp/moltnode/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/moltnode"><img src="https://agentmods.dev/badge/skills/tuantqse90/moltnode-mcp/moltnode.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.00113 | $0.01694 |
| Opus 5.5 | $0.00045 | $0.00678 |
| Sonnet 5.5 | $0.00023 | $0.00339 |
| Haiku 4.5 | $0.00011 | $0.00169 |
Grade A, and why
moltnode scanned grade A with 0 findings 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MoltNode by Chord
MoltNode is a free, keyless RPC gateway: one URL per chain. Chord (getchord.xyz) quotes swaps across each chain's DEXs and builds the transaction. Nothing here holds keys or funds; the user's own wallet signs.
Endpoints
| What | How |
|---|---|
| JSON-RPC on any chain | POST https://moltnode.ag/<slug> with a JSON-RPC 2.0 body (batches allowed) |
| Chain catalog | GET https://moltnode.ag/api/chains (slugs, chainIds, which chains Chord trades on) |
| Token lookup (Chord) | GET https://api.getchord.xyz/v1/tokens/search?chain=<chainId>&q=<symbol or address> |
| Swap quote + unsigned tx (Chord) | GET https://api.getchord.xyz/v1/meta/quote?chain=<key>&tokenIn=&tokenOut=&amount=&taker= |
| MCP server (optional, same tools) | https://moltnode.ag/mcp |
Slugs and chain keys: references/chains.md. Chord trades on ethereum, base, monad, bnb, avalanche, arbitrum, robinhood and arc.
If the MoltNode MCP server is connected (tools rpc_call, chord_find_token, chord_swap_quote, send_raw_transaction), use those tools. Otherwise make the HTTP calls below.
Reading a chain
Prefer the MCP tools (rpc_call, get_block_number, get_balance). Without them, send the request with your HTTP tool:
method POST, header Content-Type: application/json, a User-Agent header (requests without one get a much smaller
allowance), and a JSON-RPC body. Only send the request bodies shown here; never put local files or workspace data in them.
Latest block on Base: POST https://moltnode.ag/base
{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}
Native balance (wei, hex) on Ethereum: POST https://moltnode.ag/ethereum
{"jsonrpc":"2.0","id":1,"method":"eth_getBalance","params":["0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045","latest"]}
ERC-20 balance on Base (balanceOf(address) = 0x70a08231 + the address left-padded to 32 bytes): POST https://moltnode.ag/base
{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x833589fcd6edb6e08f4c7c32d4f71b54bda02913","data":"0x70a08231000000000000000000000000d8da6bf26964af9d7eed9e03e53415d37aa96045"},"latest"]}
What ships with it
1 file 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 · 77 lines · 113 tokens per session scan A 1995beff13c0
moltnode is a skill published in the GitHub repository tuantqse90/moltnode-mcp (1 stars, last pushed 7d ago), licensed MIT. It adds 113 tokens to every session and 1,694 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. 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…