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 agentmods add skills/smartcontractkit/chainlink-agent-skills/chainlink-data-feeds-skillnpx skills add smartcontractkit/chainlink-agent-skills --skill chainlink-data-feeds-skillgit clone --depth 1 https://github.com/smartcontractkit/chainlink-agent-skillsWrote 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/smartcontractkit/chainlink-agent-skills/chainlink-data-feeds-skill)<a href="https://agentmods.dev/skills/smartcontractkit/chainlink-agent-skills/chainlink-data-feeds-skill"><img src="https://agentmods.dev/badge/skills/smartcontractkit/chainlink-agent-skills/chainlink-data-feeds-skill.svg" alt="Measured on agentmods" 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.00122 | $0.01522 |
| Opus 5 | $0.00061 | $0.00761 |
| Sonnet 5 | $0.00024 | $0.00304 |
| Haiku 4.5 | $0.00012 | $0.00152 |
Grade A, and why
chainlink-data-feeds-skill 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 7d 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.
3. When a fetch is needed, apply the cascade: WebFetch first; if it returns <1000 chars of useful content, fall back to `curl -s -L -A "Mozilla/5.0 ..." "<url>"`; if both fail, report the URL to the user. How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chainlink Data Feeds Skill
Overview
Route Data Feed requests to the simplest valid path. Generate working code on first attempt when possible. Fetch documentation only when a specific gap blocks progress.
Progressive Disclosure
- Keep this file as the default guide.
- Read references/reading-price-feeds.md only when the user wants to read a price feed on EVM, write a consumer contract, read off-chain, look up AggregatorV3Interface, or debug a price feed integration.
- Read templates/starter-kit/README.md and the files in templates/starter-kit when the user asks for a working example project, Foundry starter kit, runnable Data Feeds example, or says something like "give me a working example of a data feeds project." Use this starter-kit template instead of inventing project scaffolding.
- Read references/mvr-feeds.md only when the user asks about Multiple-Variable Response feeds, bundle feeds, or BundleAggregatorProxy.
- Read references/svr-feeds.md only when the user asks about Smart Value Recapture, OEV recapture, or searcher onboarding.
- Read references/feed-types.md only when the user asks about feed categories, SmartData/RWA, rates/volatility, tokenized equity feeds, or needs help choosing a feed type.
- Read references/multi-chain.md only when the user targets Solana, StarkNet, Aptos, or Tron.
- Read references/feed-operations.md only when the user asks about L2 sequencer uptime checks, feed deprecation, contract registry, developer responsibilities, or data sources.
- Read references/official-sources.md only when the answer depends on live data that the reference files do not contain -- feed addresses for a specific chain, current deprecation schedules, specific network parameters.
- Read references/source-code.md only when debugging interface mismatches or the user needs to inspect contract source code on GitHub.
- Do not load reference files speculatively.
What ships with it
18 files 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.
- agents/openai.yaml 246 B
- assets/chainlink-icon.png 38 KB
- assets/data-feeds-docs-index.md 132 KB
- references/feed-operations.md 12 KB
- references/feed-types.md 7.7 KB
- references/multi-chain.md 9.2 KB
- references/mvr-feeds.md 10 KB
- references/official-sources.md 3.9 KB
- references/reading-price-feeds.md 14 KB
- references/source-code.md 4.9 KB
- references/svr-feeds.md 6.6 KB
- templates/starter-kit/foundry.toml 97 B
- templates/starter-kit/README.md 4.2 KB
- templates/starter-kit/remappings.txt 61 B
- templates/starter-kit/script/PriceFeedConsumer.s.sol 923 B
- templates/starter-kit/src/PriceFeedConsumer.sol 1.7 KB
- templates/starter-kit/test/mocks/MockV3Aggregator.sol 2.0 KB
- templates/starter-kit/test/PriceFeedConsumer.t.sol 1.4 KB
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.
- 7d ago First seen · 74 lines · 122 tokens per session scan A d8f1193c82c7
chainlink-data-feeds-skill is a skill published in the GitHub repository smartcontractkit/chainlink-agent-skills (126 stars, last pushed 2d ago), licensed MIT. It adds 122 tokens to every session and 1,522 once invoked, about $0.0006 per session on Opus 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-08-30.
Other skills, from other repositories
web3-fullstack-packaged-build
Systematic full-stack Web3 build with mandatory packaging and delivery phase.
web3-fullstack-systematic-build
Systematic approach to building full-stack Web3 applications layer by layer.
solana-dev
Use when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "fuzz my Solana program", "deploy to devnet", "send a v1 transaction", "support larger transactions", "fix maxSupportedTransactionVersion", or "explain…
devtools-event-client
Create typed EventClient for a library. Define event maps with typed payloads, pluginId auto-prepend namespacing, emit()/on()/onAll()/onAllPluginEvents() API. Connection lifecycle (5 retries, 300ms), event queuing, enabled/disabled state, SSR fallbacks, singleton pattern. Unique pluginId requirement to avoid event…
walkeros-create-destination
Use when creating a new walkerOS destination to send events to a vendor or API (GA4/gtag, Meta/Facebook Pixel, Mixpanel, Amplitude, a custom HTTP API, Measurement Protocol), web or server-side. Example-driven workflow: research the vendor SDK and define step examples before implementing the destination interface, env…
walkeros-create-source
Use when creating a new walkerOS source to capture events (browser source, dataLayer interception, server/HTTP source, webhook receiver, event capture), web or server-side. Example-driven workflow: research the input format and define step examples before implementing the push interface, createTrigger, and env pattern.