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/rstackjs/agent-skills/rstack-eco-ci-debugnpx skills add rstackjs/agent-skills --skill rstack-eco-ci-debuggit clone --depth 1 https://github.com/rstackjs/agent-skillsWhat 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.00137 | $0.04674 |
| Opus 5 | $0.00068 | $0.02337 |
| Sonnet 5 | $0.00027 | $0.00935 |
| Haiku 4.5 | $0.00014 | $0.00467 |
Grade A, and why
rstack-eco-ci-debug 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 2d 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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rstack Eco CI Debug
Use this skill to debug Rstack ecosystem CI failures without over-blaming the first upstream commit that appears red in status data.
Supported ecosystems are rspack, rsbuild, rslib, rspress, rstest, and rsdoctor. Each maps to origin/data:<ecosystem>.json in rstack-ecosystem-ci.
Choose the ecosystem before investigating. In this skill:
selected ecosystemorupstreamis the project whose commit produced the status row, for examplerslibinrslib.json.suiteis a downstream project tested against that upstream artifact, for example therspresssuite insiderslib.json.- Never infer the selected ecosystem from the failing suite name.
Ecosystem Priority
Treat rspack as the primary ecosystem because it has the broadest downstream matrix and is normally the highest-volume source of eco-ci failures.
- For an all-ecosystem request, inspect and live-verify
rspackfirst, then continue throughrsbuild,rslib,rspress,rstest, andrsdoctor. - Put the Rspack row first in summary matrices and put current
rspack/<suite>failure sections before failures from other ecosystems. - Priority controls ordering and investigation attention, not coverage. Never stop after Rspack when the requested scope includes other ecosystems.
Preconditions
Use local checkout paths already supplied by the user or automation. If a required path is missing, ask for that specific path; do not assume machine-specific paths.
- Local upstream checkout — required for inspecting commits and reviewing PR diffs. Ask for the selected ecosystem's checkout before running
git -C <upstream-path>unless the user or automation already provided it. - Local downstream project checkout — required for reproduction edits. Ask for it before making approved temporary changes to
package.json,pnpm-lock.yaml, or equivalent package-manager files. - Local
rstack-ecosystem-cicheckout — optional. If available, useorigin/data:<ecosystem>.jsonas the first local status source. Pass the checkout path toscripts/ecosystem-status.sh --ecosystem <ecosystem> --repo <ecosystem-ci-path>. - GitHub access — prefer authenticated
ghfor the upstream repository andrstackjs/rstack-ecosystem-ci. Ifghis unavailable, use the matchingorigin/data:<ecosystem>.json, workflow/job URLs, and the GitHub connector or public pages where available; state any evidence gap in the report.
What ships with it
7 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.
- 2d ago First seen · 307 lines · 137 tokens per session scan A 0c4bad9ff334
rstack-eco-ci-debug is a skill published in the GitHub repository rstackjs/agent-skills (90 stars, last pushed 6d ago), licensed MIT. It adds 137 tokens to every session and 4,674 once invoked, about $0.0007 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
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
dsh-web-pre-push-checks
Use before pushing, opening or updating a pull request, or claiming dsh-web checks pass. Selects the required repository gates and diff-specific generation, build, and GUI evidence.
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
harness-setup
HAR: Project init, tool setup, agent config, memory setup, skill mirror sync. Trigger: setup, init, new project, CI/Codex setup, harness-mem, mirror. Do NOT load for: implementation, review, release, planning.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.