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 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/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.
<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="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium MCP Rug Pull · line 42 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00064 | $0.00694 |
| Opus 5.5 | $0.00026 | $0.00278 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (93 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 694 once invoked, about $0.0003 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…