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 goldsky-io/goldsky-agent --skill turbo-buildergit 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/skills/goldsky-io/goldsky-agent/turbo-builder)<a href="https://agentmods.dev/skills/goldsky-io/goldsky-agent/turbo-builder"><img src="https://agentmods.dev/badge/skills/goldsky-io/goldsky-agent/turbo-builder/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/goldsky-io/goldsky-agent/turbo-builder"><img src="https://agentmods.dev/badge/skills/goldsky-io/goldsky-agent/turbo-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
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.00202 | $0.02855 |
| Opus 5.5 | $0.00081 | $0.01142 |
| Sonnet 5.5 | $0.00040 | $0.00571 |
| Haiku 4.5 | $0.00020 | $0.00285 |
Grade A, and why
turbo-builder 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 2d 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Builder
Boundaries
- Build NEW pipelines. Do not diagnose broken pipelines — that belongs to
/turbo-doctor. - Do not serve as a YAML reference. If the user only needs to look up a field or syntax, use the
/turbo-pipelinesskill instead. - For dataset lookups, use
/datasets. - A REST lookup of one wallet's balances or transfers, token prices, a wallet's Polymarket activity, positions or balances, or a block by number, hash or timestamp is
/feeds. Build a pipeline only when the rows need to land in the user's own database or webhook.
Walk the user through building a complete pipeline from scratch, step by step. Generate a valid YAML configuration, validate it, and deploy it.
Builder Workflow
Step 1: Verify Authentication
Run goldsky project list 2>&1 to check login status.
- If logged in: Note the current project and continue.
- If not logged in: Use the
/auth-setupskill for guidance.
Step 2: Understand the Goal
Ask the user what they want to index. Good questions:
- What blockchain/chain? (Ethereum, Base, Polygon, Solana, etc.)
- What data? (transfers, swaps, events from a specific contract, all transactions, etc.)
- Where should the data go? (PostgreSQL, ClickHouse, Kafka, S3, etc.)
- Do they need transforms? (filtering, aggregation, enrichment)
- One-time backfill or continuous streaming?
If the user already described their goal, extract answers from their description.
Step 3: Choose the Dataset
Use the /datasets skill to find the right dataset.
Key points:
- Common datasets:
<chain>.raw_logs,<chain>.raw_transactions,<chain>.erc20_transfers,<chain>.raw_traces - For decoded contract events on EVM chains: source from
<chain>.raw_logswith a filter onaddressONLY, then add a SQL transform that calls_gs_log_decode(_gs_fetch_abi(<explorer-url>, <source>), topics, data) AS decoded, then filter downstream byWHERE decoded.event_signature = '<EventName>(<types>)'. Never put topic0 hashes in the source filter — see/turbo-transformsfor the full pattern. There is no consumable<chain>.decoded_logsdataset; decoding always happens in a transform. - For pre-decoded common token events:
<chain>.erc20_transfers,<chain>.erc721_transfers,<chain>.erc1155_transfersare available and don't need decoding transforms. - For Solana: use
solana.transactions,solana.token_transfers, etc.
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.
- 2d ago Changed dd1012276d81
- 25d ago Changed · +15 tokens per session 398b69fbd157
- 28d ago Changed · +1 lines · +23 tokens per session a95fe9593909
- 1mo ago Changed · +45 tokens per session 7a58b0c34c11
- 1mo ago Changed · +10 lines 5a560c6a8167
- 2mo ago First seen · 208 lines · 119 tokens per session scan A 3dbb69504202
turbo-builder is a skill published in the GitHub repository goldsky-io/goldsky-agent (12 stars, last pushed yesterday), licensed MIT. It adds 202 tokens to every session and 2,855 once invoked, about $0.0008 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-08-30.
Other skills, from other repositories
cli-anything-eth2-quickstart
Use eth2-quickstart to autonomously deploy a hardened Ethereum node, install execution and consensus clients, configure validator metadata, expose RPC safely, and inspect node health with structured JSON output.
devloop
Goal-driven development loop — define objective, write rules with key-results, verify visually, sync to issue tracker.
skill0
Root index of x-cmd skill0 sub-skills. Defines the OKR-style agent workflow (goal → rule-verified results → execute), skill discovery, and agent tooling preferences. Style: principle-first, concise, delegate specifics to authoritative external sources.
multichain-deployment
Use when deploying the same protocol to multiple chains at the same address. Covers CREATE2 for deterministic addresses, deployment registries, chain-specific configuration, multi-chain testing, and canonical deployment patterns.
l2-deployment
Use when deploying contracts to L2 networks (Base, Optimism, Arbitrum). Covers L2-specific considerations, PUSH0 compatibility, gas estimation, L1 data costs, bridge integration, and deployment scripts.
blockchain-infrastructure
Use this skill when asked about blockchain node deployment, RPC infrastructure, CI/CD for smart contracts, monitoring and alerting for blockchain networks, MEV infrastructure (Flashbots, builders, relays), key management (KMS, HSM), and environment management for devnet/testnet/staging/mainnet. Languages: Go, Rust…