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 paultyng/skill-issue --skill review-cigit clone --depth 1 https://github.com/paultyng/skill-issueWrote 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/paultyng/skill-issue/review-ci)<a href="https://agentmods.dev/skills/paultyng/skill-issue/review-ci"><img src="https://agentmods.dev/badge/skills/paultyng/skill-issue/review-ci/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/paultyng/skill-issue/review-ci"><img src="https://agentmods.dev/badge/skills/paultyng/skill-issue/review-ci.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00059 | $0.01831 |
| Opus 5 | $0.00030 | $0.00915 |
| Sonnet 5 | $0.00012 | $0.00366 |
| Haiku 4.5 | $0.00006 | $0.00183 |
Grade A, and why
review-ci scanned grade A with 1 finding 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 9d 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Findings must cite probed evidence (`path:line`, grep output, command result), not pattern-matched suspicion. Per `~/.claude/rules/probe-not-assume.md`. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI / Workflow Review
Structured review of CI/CD pipeline configuration. Focus is on GitHub Actions (the dominant case); CircleCI / Buildkite / GitLab / Jenkins are noted where they share concerns but receive lighter coverage.
Out of scope (defer to siblings):
- Application source code →
review-code - Container images and Dockerfiles →
review-infrastructure - Application-level secrets and IAM →
review-security
Workflow
1. Scope and explore
- Confirm scope with the user: full repo CI config, specific workflow(s), or changed files only (PR or branch diff).
- Resolve scope to a file list. Based on what the user requested:
- Changed files (PR or branch): Run
git diff --name-only --diff-filter=d <base>...HEAD. If the user references a PR number, usegh pr diff <number> --name-onlyinstead. Filter to CI file types (see classification below). - Explicit paths: Include all CI files under given directories.
- Full repo: Walk for CI files (default).
- Changed files (PR or branch): Run
- If invoked from review-all: receive
file_list,has_changes,base_ref,REVIEW_DIR, andpr_urlfrom the orchestrator. Skip your own scope confirmation.
File classification. Detect by path and content:
- GitHub Actions workflows:
.github/workflows/*.yml,.github/workflows/*.yaml - Composite / reusable actions:
action.ymloraction.yamlfiles (any location, but typically.github/actions/*/action.yml) - Dependabot / Renovate config:
.github/dependabot.yml,renovate.json,.renovaterc* - CircleCI:
.circleci/config.yml - Buildkite:
.buildkite/pipeline.yml,.buildkite/*.yml - GitLab CI:
.gitlab-ci.yml - Jenkins:
Jenkinsfile - Other:
azure-pipelines.yml,cloudbuild.yaml,bitbucket-pipelines.yml,wercker.yml
2. System overview
Produce a brief pipeline summary covering:
- Triggers in use:
push,pull_request,pull_request_target,workflow_dispatch,schedule,workflow_call,release - Branches / paths gated
- Reusable workflows or composite actions referenced
- Self-hosted vs. GitHub-hosted runners
- Secrets / OIDC providers in use (named, not values)
- Deploy targets (if discernible)
What ships with it
1 file 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.
- 9d ago First seen · 165 lines · 59 tokens per session scan A 92766fd0bf78
review-ci is a skill published in the GitHub repository paultyng/skill-issue (9 stars, last pushed 28d ago), licensed MIT. It adds 59 tokens to every session and 1,831 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
megalinter-setup
Install or upgrade MegaLinter on a repository. Use when the user wants to add MegaLinter to a project, set up linting CI, update MegaLinter configuration or version, or says "install megalinter", "setup linting", "add code quality checks". Always goes through npx mega-linter-runner (--install or --upgrade), then…
gh-fix-ci
Diagnose failing GitHub Actions checks on a PR via gh, summarize the failure context, propose a plan, and only implement after explicit user approval. External CI providers (Buildkite, CircleCI, etc.) are reported by URL only.
megalinter
Entry point for everything MegaLinter. Use when the user wants to lint their repository, set up MegaLinter, check or fix lint errors, make CI lint jobs pass, or says "run megalinter", "fix lint errors", "make the linters happy", "clean up code quality". Detects the repository state and orchestrates the…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
Checkly Monitoring as Code
Teach agents to build synthetic monitoring as code with Checkly, including Playwright browser checks, API checks, alerting, and CI deploy workflows.
skillnote
Self-hosted skill registry for OpenClaw. Stores procedures your team writes (name, description, body), syncs them to disk before each task, and collects which-helped/which-failed signals from the agent so the registry improves over time.