feeds

feeds is a skill for Claude Code from goldsky-io/goldsky-agent. It costs 139 tokens per session (2,757 once invoked), scanned A, original, MIT.

A guide for querying Goldsky Feeds, an HTTP service that returns one wallet's balances, transfers, and portfolio values across supported blockchain networks.

In plain words
What is it for?
Use it to inspect wallet holdings, portfolio value, transfer history, or deposits through the Feeds API.
Why use it?
It prevents confusion between the Feeds API key, the CLI login token, and other Goldsky products, and clarifies that Feeds does not stream data into your database.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Part of the goldsky plugin — 19 skills, 1 command, 1 agent shipped together

Good fit Use it to inspect wallet holdings, portfolio value, transfer history, or deposits through the Feeds API.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/goldsky-io/goldsky-agent/feeds
Install

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.

Any agent
npx skills add goldsky-io/goldsky-agent --skill feeds
Clone the repo
git clone --depth 1 https://github.com/goldsky-io/goldsky-agent

Made for: Claude Code.

Or install goldsky, the plugin that ships this one along with the rest of its 19 skills, 1 command, 1 agent.

Wrote 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.

agentmods badge for feeds

README.md
[![agentmods](https://agentmods.dev/badge/skills/goldsky-io/goldsky-agent/feeds/github.svg)](https://agentmods.dev/skills/goldsky-io/goldsky-agent/feeds)
Your own site
<a href="https://agentmods.dev/skills/goldsky-io/goldsky-agent/feeds"><img src="https://agentmods.dev/badge/skills/goldsky-io/goldsky-agent/feeds/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.

agentmods 80×15 button for feeds

Your own site · 80×15
<a href="https://agentmods.dev/skills/goldsky-io/goldsky-agent/feeds"><img src="https://agentmods.dev/badge/skills/goldsky-io/goldsky-agent/feeds.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 139 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,757 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 6 Oct 2026
  • Snyk pass 7 Oct 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00139 $0.02757
Opus 5.5 $0.00056 $0.01103
Sonnet 5.5 $0.00028 $0.00551
Haiku 4.5 $0.00014 $0.00276

Measured 8d ago against content hash 7420bb3f2eb3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

feeds 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 8d 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.

curl -sS -H "x-api-key: $GOLDSKY_FEEDS_API_KEY" \
skills/feeds/SKILL.md · 82 lines

How it starts

The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Goldsky Feeds

Feeds answers one question about one wallet over HTTP: what it holds, or what it sent and received, across the supported chains in a single request. Goldsky indexes, normalizes, and prices the rows. The caller does not run a pipeline.

The same host and the same key also serve Polymarket and block-header feeds. Those are listed under "Other feeds on this key", and they do not follow the conventions below.

The CLI gets the key (goldsky feeds key reveal); the feeds themselves are plain HTTP. There are no goldsky feeds read commands. Do not mint the key with goldsky edge create. The endpoint name feeds is reserved on the Edge create path, so that command is rejected. The CLI login token is a different credential and does not authenticate these requests. Do not print the Feeds key.

When this is the wrong tool

  • The rows need to land in the user's own database or webhook. That is a Turbo pipeline (/turbo-builder, /datasets). Feeds does not stream into a sink; streaming is not offered yet (https://docs.goldsky.com/feeds/streaming).
  • The question is a Turbo dataset name or chain prefix. That is /datasets. Those prefixes differ: Feeds says polygon and arbitrum_one, Turbo says matic and arbitrum.
  • The question is JSON-RPC. That is /edge, or /boost when they want to keep their current provider.

Key

A project has one Feeds key, and every feed answers it. Get it with the CLI. Do not send the user to the dashboard, and do not run goldsky edge create.

goldsky feeds key reveal
export GOLDSKY_FEEDS_API_KEY="$(cat "$HOME/.goldsky/feeds-api-key")"

reveal creates the key if the project has none, otherwise fetches the existing one, and writes it to ~/.goldsky/feeds-api-key (mode 600). It never prints the key and never rotates it, so it is safe to run again. Do not cat that file into the chat, and do not write the key anywhere else.

Success prints Created Feeds API key and saved it to ~/.goldsky/feeds-api-key or Saved existing Feeds API key to ~/.goldsky/feeds-api-key. If it prints the general help instead, the CLI is older than 13.17.0 (an older CLI exits 0 there, so read the output, not the exit code); run /auth-setup to install the pinned version. Do not pass --token. A 401 means they are not logged in: use /auth-setup first. A 403 means the user is not an Editor on the project. A 409 means an Edge endpoint named feeds exists and is not the Feeds key; that endpoint has to be deleted first.

Read the full file on GitHub · 82 lines

Changes

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.

  1. 8d ago Changed · -29 lines · +4 tokens per session 7420bb3f2eb3
  2. 19d ago Changed · +20 lines · +24 tokens per session 860d5bbdff63
  3. 22d ago First seen · 91 lines · 111 tokens per session scan A eaf04222e622

Subscribe to this mod's changes

feeds is a skill published in the GitHub repository goldsky-io/goldsky-agent (12 stars, last pushed 2d ago), licensed MIT. It adds 139 tokens to every session and 2,757 once invoked, about $0.0006 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-03.