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.
git clone --depth 1 https://github.com/goldsky-io/goldsky-agentWrote 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/plugins/goldsky-io/goldsky-agent/goldsky-data)<a href="https://agentmods.dev/plugins/goldsky-io/goldsky-agent/goldsky-data"><img src="https://agentmods.dev/badge/plugins/goldsky-io/goldsky-agent/goldsky-data/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/plugins/goldsky-io/goldsky-agent/goldsky-data"><img src="https://agentmods.dev/badge/plugins/goldsky-io/goldsky-agent/goldsky-data.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
goldsky-data 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 17d 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.
What it actually says
{
"name": "goldsky-data",
"displayName": "Goldsky (data)",
"source": "./",
"description": "Index, query and monitor onchain data across 150+ chains. Real-time pipelines into PostgreSQL, ClickHouse, Kafka and more, hosted subgraphs, and managed RPC — for reserve and circulating-supply reporting, transfer and sanctions monitoring, deposit detection, cross-chain transfer tracking, reconciliation, wallet balance and history APIs, tokenized-asset holder registries, and prediction-market datasets such as Polymarket.",
"version": "1.7.6",
"category": "data-and-analytics",
"keywords": [
"goldsky",
"blockchain",
"onchain-data",
"indexing",
"pipelines",
"subgraphs",
"rpc",
"boost",
"analytics",
"compliance-monitoring",
"prediction-markets",
"wallets",
"data"
],
"skills": [
"./skills/turbo-builder",
"./skills/turbo-doctor",
"./skills/turbo-pipelines",
"./skills/turbo-transforms",
"./skills/turbo-operations",
"./skills/mirror",
"./skills/mirror-doctor",
"./skills/subgraph-builder",
"./skills/subgraph-doctor",
"./skills/subgraph-migrate",
"./skills/boost",
"./skills/edge",
"./skills/datasets",
"./skills/secrets",
"./skills/auth-setup"
]
}What it installs
The manifest is a name and a version. 15 skills travel with it, and installing the plugin installs all of them — 2,367 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill datasets A 215 tokens
- Skill mirror A 154 tokens
- Skill turbo-pipelines A 133 tokens
- Skill boost A 120 tokens
- Skill secrets A 135 tokens
- Skill subgraph-doctor A 214 tokens
- Skill edge A 165 tokens
- Skill mirror-doctor A 142 tokens
- Skill turbo-builder A 202 tokens
- Skill turbo-transforms A 126 tokens
- Skill subgraph-builder A 239 tokens
- Skill turbo-operations A 100 tokens
- Skill subgraph-migrate A 186 tokens
- Skill turbo-doctor A 87 tokens
- Skill auth-setup B 149 tokens
What ships with it
2 files beside marketplace.json#goldsky-data 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.
- 17d ago Changed 088a3cef8b3c
- 18d ago Changed 9e47667d1f97
- 20d ago First seen · 40 lines scan A 74d16dad19d3
goldsky-data is a plugin published in the GitHub repository goldsky-io/goldsky-agent (12 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-29.
Other plugins, from other repositories
uniswap-cca
Configure and deploy Continuous Clearing Auction (CCA) smart contracts for token distribution.
pandects
Executable credit laws with broken specimens and reduced counterexamples.
pancakeswap-v2-plugin
Swap tokens and manage liquidity on PancakeSwap V2 (xyk AMM) on BSC, Base, and Arbitrum. Triggers: swap pancakeswap v2, add/remove liquidity pancake, pcs v2 quote, check pancake pair.
aerodrome-amm-plugin
Swap tokens and provide liquidity on Aerodrome AMM (volatile/stable pools) on Base.
sparklend-plugin
SparkLend lending and borrowing on Ethereum Mainnet — supply, withdraw, borrow, repay, positions, health factor, reserves.
stablecoin-depeg-monitor
Stablecoin peg stability monitoring and historical depeg database. Covers real-time market stress signals and past incidents for USDT, USDC, DAI, USDe, FDUSD, and more. Also peg/reserve risk monitoring for treasuries and custodians.