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 chord-chartsgit 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-charts)<a href="https://agentmods.dev/skills/tuantqse90/moltnode-mcp/chord-charts"><img src="https://agentmods.dev/badge/skills/tuantqse90/moltnode-mcp/chord-charts/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-charts"><img src="https://agentmods.dev/badge/skills/tuantqse90/moltnode-mcp/chord-charts.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.00121 | $0.00840 |
| Opus 5.5 | $0.00048 | $0.00336 |
| Sonnet 5.5 | $0.00024 | $0.00168 |
| Haiku 4.5 | $0.00012 | $0.00084 |
Grade A, and why
chord-charts 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chord charts
Chord indexes every DEX swap on its chains and builds candles from those trades. scripts/chart.py turns them into a standalone SVG candlestick chart and prints a JSON summary.
Draw a chart
python3 scripts/chart.py --chain base --token AERO --tf 1h --limit 48
python3 scripts/chart.py --chain solana --token BONK --tf 15m --limit 96
python3 scripts/chart.py --chain robinhood --token NVDA --tf 1d --limit 60
python3 scripts/chart.py --chain arbitrum --token 0x912ce59144191c1204e64559fe8253a0e49e6548 --tf 4h --limit 42 --out arb.svg
--chain:ethereum,base,monad,bnb,avalanche,arbitrum,robinhood,arc,solana.--token: a symbol or name, or an address (0x…on EVM chains, the base58 mint on Solana, case-sensitive). A symbol is resolved through Chord's search; the script prints the address it picked. Similar tickers are common: if the user named a token loosely, show them the resolved address.--tf:1m 5m 15m 1h 4h 1d 1w(Solana up to1d).--limit: number of candles, up to 1000.- Output: the SVG file (path in the summary, default
chart-<symbol>-<chain>-<tf>.svg) and a JSON summary on stdout:symbol,token,open,close,changePct,high,low,volumeUsd,trades,lastCandleOpen.
Show the user the chart file and a one-line read of the summary, for example: "AERO on Base, last 48 hours: $0.884, -2.75%, range $0.831 to $0.920, $10.5M traded."
Notes
- Prices are in USD from on-chain trades. Wrapped majors stand in for the coin: WETH for ETH, cbBTC on Base, BTC.b on Avalanche, BTCB on BNB Chain, WMON on Monad. Say which token you charted.
- Robinhood Chain stock tokens trade around the clock on-chain, so their candles can move while the US market is closed.
- Solana candles are one pool's prices (the main pool), not a blend across pools.
- If the last candle is still open,
lastCandleOpenis true and the subtitle says so. - About 60 requests a minute without a key; a chart costs one or two requests.
- For raw data without a chart:
GET https://api.getchord.xyz/v1/candles?chain=<chainId>&token=<address>&tf=1h&limit=48(EVM) orGET https://api.getchord.xyz/v1/chains/solana/token/<mint>/candles?tf=1h&limit=48.
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 · 39 lines · 121 tokens per session scan A c0706181f6cf
chord-charts is a skill published in the GitHub repository tuantqse90/moltnode-mcp (1 stars, last pushed 7d ago), licensed MIT. It adds 121 tokens to every session and 840 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…