Borrowing it
Nothing to install: this file belongs to priyanshuchawda/tracepilot-gemini-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/priyanshuchawda/tracepilot-gemini-cli/main/.gemini/skills/ci/SKILL.mdgit clone --depth 1 https://github.com/priyanshuchawda/tracepilot-gemini-cliWrote 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/priyanshuchawda/tracepilot-gemini-cli/ci)<a href="https://agentmods.dev/skills/priyanshuchawda/tracepilot-gemini-cli/ci"><img src="https://agentmods.dev/badge/skills/priyanshuchawda/tracepilot-gemini-cli/ci.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.1 | $0.00042 | $0.00727 |
| Opus 5 | $0.00021 | $0.00364 |
| Sonnet 5 | $0.00008 | $0.00145 |
| Haiku 4.5 | $0.00004 | $0.00073 |
Grade A, and why
ci 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 7d 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.
This is a copy
100% identical to ci — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Replicate & Status
This skill enables the agent to efficiently monitor GitHub Actions, triage failures, and bridge remote CI errors to local development. It defaults to automatic replication of failures to streamline the fix cycle.
Core Capabilities
- Automatic Replication: Automatically monitors CI and immediately executes suggested test or lint commands locally upon failure.
- Real-time Monitoring: Aggregated status line for all concurrent workflows on the current branch.
- Fail-Fast Triage: Immediately stops on the first job failure to provide a structured report.
Workflow
1. CI Replicate (replicate) - DEFAULT
Use this as the primary path to monitor CI and automatically replicate failures locally for immediate triage and fixing.
- Behavior: When this workflow is triggered, the agent will monitor the CI and immediately and automatically execute all suggested test or lint commands (marked with 🚀) as soon as a failure is detected.
- Tool:
node .gemini/skills/ci/scripts/ci.mjs [branch] - Discovery: The script automatically finds the latest active or recent run for the branch. Do NOT manually search for run IDs.
- Goal: Reproduce the failure locally without manual intervention, then proceed to analyze and fix the code.
1. CI Status (status)
Use this when you have pushed changes and need to monitor the CI and reproduce any failures locally.
- Tool:
node .gemini/skills/ci/scripts/ci.mjs [branch] [run_id] - Discovery: The script automatically finds the latest active or recent run for the branch. You should NOT manually search for `run_id` using `gh run list` unless a specific historical run is requested. Simply provide the branch name.
- Step 1 (Monitor): Execute the tool with the branch name.
- Step 2 (Extract): Extract suggested `npm test` or `npm run lint` commands from the output (marked with 🚀).
- Step 3 (Reproduce): Execute those commands locally to confirm the failure.
- Behavior: It will poll every 15 seconds. If it detects a failure, it will exit with a structured report and provide the exact commands to run locally.
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.
- 7d ago First seen · 67 lines · 42 tokens per session scan A 2f6c8c68cc4e
ci is a skill published in the GitHub repository priyanshuchawda/tracepilot-gemini-cli (1 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 727 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ci, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
glab-cli
GitLab CLI (glab) reference and workflow for repository, merge request, issue, CI/CD, release, and API operations across GitLab.com and self-managed or dedicated instances. Use when Codex needs to run or explain glab commands, usually by relying on the current glab context first, and only falling back to git remote -v…
lov-release-via-cicd
A release workflow for Node, Tauri, Vite, shell, and GitHub Release projects. It checks or configures automated versioning and publishing, including macOS signing and notarisation when relevant.
lefthook
Canonical lefthook git-hooks setup: pre-commit (format, check, secret scan) and pre-push (test), each delegating to mise run tasks. Use for git hook configuration.
shipping-and-launch
Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
gitlab
GitLab issues, merge requests, repositories, CI pipelines, and code search via the glab CLI. Use when the user mentions GitLab, an MR/issue number, a project on gitlab.com, or a self-hosted GitLab instance.
release
Trigger the CI release pipeline for gemini-plugin-cc. Maintainer-only.