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-cre-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-cre-skill)<a href="https://agentmods.dev/skills/smartcontractkit/chainlink-agent-skills/chainlink-cre-skill"><img src="https://agentmods.dev/badge/skills/smartcontractkit/chainlink-agent-skills/chainlink-cre-skill.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector warn
SkillSpector: 3 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 24 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.
- high Privilege Escalation · line 60 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 60 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.00125 | $0.02779 |
| Opus 5 | $0.00063 | $0.01389 |
| Sonnet 5 | $0.00025 | $0.00556 |
| Haiku 4.5 | $0.00013 | $0.00278 |
Grade A, and why
chainlink-cre-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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chainlink CRE Skill
Overview
Route CRE requests to the simplest valid path. Keep this file as the decision layer; load reference files only for the mechanics needed by the user's request. Generate working workflow code on first attempt when the user asks for implementation.
Progressive Disclosure
- Keep this file as the default guide.
- Read references/getting-started.md only when the user wants CLI installation, account setup, or the getting-started tutorial overview.
- Read references/project-scaffolding.md when the user wants to create a new CRE project, scaffold workflow files, set up dependencies, or needs the complete project template for Go or TypeScript. Always read this file before generating a new project from scratch.
- Read references/simulation.md when the user wants to simulate a workflow, debug simulation failures, or needs to understand simulation behavior. Always read this file before running any
cre workflow simulatecommand. - Read references/workflow-patterns.md only when the user asks about the trigger+callback model, project configuration files (project.yaml, workflow.yaml, config.json, secrets.yaml), secrets management, DON Time, or randomness.
- Read references/triggers.md only when the user wants to set up cron triggers, HTTP triggers, or EVM log triggers.
- Read references/evm-client.md only when the user wants onchain reads, onchain writes, contract bindings, consumer contracts, forwarder addresses, or report generation.
- Read references/http-client.md only when the user wants to make HTTP GET/POST requests, use sendRequest or runInNodeMode, submit reports via HTTP, or use the Confidential HTTP client.
- Read references/confidential-workflows.md when the user wants a handler to execute inside a TEE/enclave, mentions Confidential Workflows,
handlerInTee/cre.HandlerInTee,TeeRuntime, enclave attestation, or asks how to hide workflow data from node operators. Read it before writing any confidential workflow code, and read it to tell Confidential Workflows apart from the Confidential HTTP client inhttp-client.md— the two are different capabilities whose APIs do not mix. - Read references/sdk-reference.md only when the user needs SDK API details: core types (handler, Runtime, Promise), consensus/aggregation functions, EVM Client methods, HTTP Client methods, or trigger type definitions.
- Read references/cli-reference.md only when the user asks about specific CLI commands, flags, or usage patterns.
- Read references/operations.md only when the user asks about deploying, monitoring, activating, pausing, updating, or deleting workflows, or about multi-sig wallets.
- Read references/concepts.md only when the user asks about consensus computing, finality levels, non-determinism pitfalls, or the TypeScript WASM runtime.
- Read references/domain-patterns.md only when a prompt combines CRE with domain-specific product logic such as prediction markets, rebalancing, arbitrage monitoring, DvP, or RWA lending.
- Read references/official-sources.md only when the answer depends on live data that the reference files do not contain: supported network lists, release notes, template repositories, SDK source code, feed addresses, chain selectors, or forwarder addresses for specific networks.
- Read references/chain-selectors.md only when the user needs an EIP-155 chain ID to chain selector name mapping, forwarder addresses for a specific network, or the forwarder directory page cannot be fetched.
- Read references/feedback.md only when a feedback-loop trigger has fired in the current session (see "Feedback Loop" below): a content gap in the references, or user-voiced pain about this skill. Do not load it speculatively.
- Do not load reference files speculatively.
What ships with it
19 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 248 B
- assets/chainlink-icon.png 38 KB
- assets/cre-docs-index.md 203 KB
- references/chain-selectors.md 5.3 KB
- references/cli-reference.md 12 KB
- references/concepts.md 9.1 KB
- references/confidential-workflows.md 18 KB
- references/domain-patterns.md 3.2 KB
- references/evm-client.md 24 KB
- references/feedback.md 7.4 KB
- references/getting-started.md 5.0 KB
- references/http-client.md 20 KB
- references/official-sources.md 6.5 KB
- references/operations.md 8.9 KB
- references/project-scaffolding.md 13 KB
- references/sdk-reference.md 22 KB
- references/simulation.md 11 KB
- references/triggers.md 8.1 KB
- references/workflow-patterns.md 16 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 · 80 lines · 125 tokens per session scan A 3efaadf97cd3
chainlink-cre-skill is a skill published in the GitHub repository smartcontractkit/chainlink-agent-skills (126 stars, last pushed 4d ago), licensed MIT. It adds 125 tokens to every session and 2,779 once invoked, about $0.0006 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
ax-go-gen
Use when writing Go code with github.com/ax-llm/ax/packages/go for AxGen programs, forward calls, indexed multi-sampling, result pickers, streaming, tools, assertions, traces, usage, and output parsing.
ax-go-agent
Use when writing Go code with github.com/ax-llm/ax/packages/go for agents, child delegation, tools, MCP, citations, persistent playbook learning, stage instructions, runtime state, final typed responses, and direct-respond executor skipping.
ax-go-audio
Use when writing Go code with github.com/ax-llm/ax/packages/go for audio input/output, OpenAI Responses audio mapping, realtime event folding, and generated package audio examples.
ax-go-llm
Use when writing Go code with github.com/ax-llm/ax/packages/go for using the generated Ax package, factory functions, package docs, examples, and API reference.
ax-go-signature
Use when writing Go code with github.com/ax-llm/ax/packages/go for string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes.
ax-go-agent-optimize
Use when writing Go code with github.com/ax-llm/ax/packages/go for agent optimization, verified agent-playbook evolution, evaluators, judges, optimizer artifacts, BootstrapFewShot, and GEPA.