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 smartcontractkit/chainlink-agent-skills --skill chainlink-ccip-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-ccip-skill)<a href="https://agentmods.dev/skills/smartcontractkit/chainlink-agent-skills/chainlink-ccip-skill"><img src="https://agentmods.dev/badge/skills/smartcontractkit/chainlink-agent-skills/chainlink-ccip-skill.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 57 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Excessive Agency · line 58 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00091 | $0.02193 |
| Opus 5 | $0.00046 | $0.01097 |
| Sonnet 5 | $0.00018 | $0.00439 |
| Haiku 4.5 | $0.00009 | $0.00219 |
Grade A, and why
chainlink-ccip-skill 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 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.
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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chainlink CCIP Skill
Overview
Route CCIP requests to the simplest valid path while keeping side effects and credential exposure out of the agent runtime.
Perform live read-only lookups and generate user-run artifacts, but never sign, broadcast, deploy, bridge, transfer, or otherwise execute an onchain write. Refuse every mainnet write workflow, including user-run write artifacts.
Progressive Disclosure
- Keep this file as the default guide.
- Read references/examples.md only when you need a concrete reference for what a good response looks like (preflight summaries, monitoring explanations, contract-generation structure).
- Read references/official-sources.md only when the answer depends on live CCIP facts, current tool behavior, route or token availability, or message-status surfaces.
- Read references/ccip-api.md whenever the answer depends on live CCIP data: message status, lane inventory, lane latency, chain or contract configuration, verifiers, or intent status.
- Read references/ccip-tools.md only when the user wants a tool-first workflow through CCIP CLI, API, or SDK.
- Read references/ccip-contracts.md only when the user wants sender or receiver contracts, token-transfer contracts, programmable token-transfer contracts, or contract setup help.
- Read references/ccip-cct.md only when the user wants to create a token, register it as a CCT, configure pools, set rate limits, or add networks for CCT operation.
- Read references/chainlink-local.md only when the user wants local simulation, local tests, or forked-environment testing for CCIP contracts.
- Read references/ccip-monitoring.md only when the user wants message lookup, monitoring, status explanation, lane performance, or failed-message diagnosis.
- Read references/ccip-discovery.md only when the user wants route connectivity checks, network classification, or supported-token discovery.
- Read references/ccip-solidity-examples.md only when generating or reviewing CCIP Solidity contracts and you need concrete code patterns (sender, receiver, token transfer, defensive receiver).
- Read references/ccip-sdk-examples.md only when the user wants TypeScript SDK usage examples for fee estimation, token transfers, messaging, or status checks.
- Read references/ccip-non-evm.md only when the user wants to work with CCIP on Solana, Aptos, Sui, TON, Canton, or any non-EVM chain family.
- Do not load reference files speculatively.
What ships with it
14 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 234 B
- assets/chainlink-icon.png 38 KB
- references/ccip-api.md 13 KB
- references/ccip-cct.md 4.9 KB
- references/ccip-contracts.md 7.9 KB
- references/ccip-discovery.md 4.2 KB
- references/ccip-monitoring.md 6.5 KB
- references/ccip-non-evm.md 14 KB
- references/ccip-sdk-examples.md 13 KB
- references/ccip-solidity-examples.md 14 KB
- references/ccip-tools.md 11 KB
- references/chainlink-local.md 11 KB
- references/examples.md 3.6 KB
- references/official-sources.md 6.5 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.
- 8d ago First seen · 132 lines · 91 tokens per session scan A cb02146386d4
chainlink-ccip-skill is a skill published in the GitHub repository smartcontractkit/chainlink-agent-skills (126 stars, last pushed 3d ago), licensed MIT. It adds 91 tokens to every session and 2,193 once invoked, about $0.0005 per session on Opus 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
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…
zevm
Build, embed, and extend the Zevm Zig execution implementation. Use for the trusted JSON-RPC development node, proof-verified light client, lazy fork runtime, Zig block execution library, C or Swift FFI integration, and native Node addon work in the evmts Zevm repository.
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…