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/tkellogg/open-strix/chainlink-workernpx skills add tkellogg/open-strix --skill chainlink-workergit clone --depth 1 https://github.com/tkellogg/open-strixWrote 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/tkellogg/open-strix/chainlink-worker)<a href="https://agentmods.dev/skills/tkellogg/open-strix/chainlink-worker"><img src="https://agentmods.dev/badge/skills/tkellogg/open-strix/chainlink-worker.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 | $0.00064 | $0.00694 |
| Opus 5 | $0.00032 | $0.00347 |
| Sonnet 5 | $0.00013 | $0.00139 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
chainlink-worker 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 4d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chainlink Backlog Worker
This skill turns chainlink issues into Codex work. It claims one issue at a time, routes it to the right repo, waits for Codex to finish, then keeps the same session alive through review rounds.
Files
worker.py— main orchestration loopprompt_builder.py— initial and review prompt buildersconfig.py— TOML config loaderpoller.py— review notifier for Keelpollers.json— poller registration
Start
From this skill directory, run:
uv run python worker.py
To use a non-default config file:
uv run python worker.py --config ~/.config/chainlink-worker/config.toml
The worker uses ~/.config/chainlink-worker/config.toml by default.
Stop
Send SIGINT or SIGTERM to the worker process. It exits cleanly after the current sleep or Codex poll interval.
Monitor
- Watch the worker stdout for lifecycle events like
issue_claimed,prompt_complete, andreview_approved - Check
chainlink session status --jsonin your chainlink working directory - Check
npx acpx codex sessions show issue-<id>in the routed repo - Check
chainlink show <id> --jsonfor labels, comments, and milestone context
Review Workflow
- Install the skill and reload pollers so
chainlink-reviewstarts firing. - When the poller reports an issue, inspect the repo changes and the Codex session.
- If changes are needed, add a review comment in chainlink:
# cd to your chainlink working directory
chainlink issue comment <id> "Please add focused regression coverage for ..." --kind human
- The worker removes
ready-for-review, re-prompts the same Codex session, then restoresready-for-review. - Approve with an explicit approval comment. Recommended:
# cd to your chainlink working directory
chainlink issue comment <id> "APPROVED" --kind resolution
The worker closes the issue and then closes the Codex session on the next poll.
Repo Routing
Configure repo routing in [repos] inside config.toml.
What ships with it
8 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.
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.
- 4d ago First seen · 79 lines · 64 tokens per session scan A ea531827f1e4
chainlink-worker is a skill published in the GitHub repository tkellogg/open-strix (85 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 694 once invoked, about $0.0003 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
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
sap-transport-overview
System-wide inventory of open transport requests — every visible modifiable request, who owns it, how big it is, and supported risk signals such as empty/local requests, explicit locks, and confirmed manifest overlaps. Headers-only and cheap; NO source diffs. Use when asked "what transports are open in the system"…
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
okx-task-watch
监听任务进展 / 帮我盯着任务 / 任务有动静告诉我 / 历史消息 / 未读消息 / 未决策 / 待决策 / 继续监听 / task watch / user watch / monitor task progress / catch me up on tasks / outstanding decisions — OKX A2A user-session task-notification monitor: live long-poll via okx-a2a user watch (also drains backlog of past/missed/unread events on entry) plus…
pm-all
Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.