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 jxoesneon/Ciel --skill cicd_integrationgit clone --depth 1 https://github.com/jxoesneon/CielWrote 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/jxoesneon/ciel/cicd_integration)<a href="https://agentmods.dev/skills/jxoesneon/ciel/cicd_integration"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/cicd_integration/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/jxoesneon/ciel/cicd_integration"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/cicd_integration.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.00019 | $0.00287 |
| Opus 5 | $0.00010 | $0.00143 |
| Sonnet 5 | $0.00004 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
cicd_integration 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 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.
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.
What it actually says
cicd_integration
Interact with CI systems.
Operations
ci.trigger(workflow, ref, inputs?)ci.status(run_id)— poll or subscribe.ci.artifacts(run_id)— list + download.ci.logs(run_id, job?)ci.list_runs(branch?, status?).
I/O Contract
io_contract:
input: { op, args }
output: { result }
idempotent: depends
side_effects: [network]
Providers
- GitHub Actions.
- GitLab CI.
- CircleCI, Buildkite, Drone (best-effort, detected from project).
Credentials resolved by secrets_manager.
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 · 42 lines · 19 tokens per session scan A 83248852320e
cicd_integration is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 19 tokens to every session and 287 once invoked, about $0.0001 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-31.
Other skills, from other repositories
lov-npm-publisher
An npm package publishing workflow that sets up releases through GitHub Actions using OIDC, a login-free trust method, or a local granular NPM token. It covers initial setup, publishing, audit checks, and verifying the package on the npm registry.
gh-ci-analyzer
A guide for using GitHub’s command-line tool to investigate failed GitHub Actions runs. GitHub Actions is GitHub’s system for automatically building, testing, and deploying code.
install-gemini-code-review-action
Installs, configures, or upgrades Dazbo's PR code review & issue triage GitHub Action (gemini-review-action) in a target repository. Use when the user wants to set up, configure, or update automated AI code reviews, issue triaging, or Gemini model workflows for their GitHub repository.
preflight
This skill should be used when the user asks to "run Preflight", "scan launch readiness", "check production readiness", "audit before deploy", "fix preflight findings", "set up preflight.yml", "wire Preflight into CI", or mentions the Preflight.sh CLI.
bash-scripting
Bash scripting workflow for creating production-ready shell scripts with defensive patterns, error handling, and testing.
ticket-spec
Turn a raw Linear Triage ticket into a fully specified ai:agent-ready one by exploring the codebase. Use when specifying, refining, or promoting tickets, or when asked why a ticket isn't dispatchable.