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/ghabix/spinecodex/pushing-ci-changesnpx skills add GhabiX/SpineCodex --skill pushing-ci-changesgit clone --depth 1 https://github.com/GhabiX/SpineCodexWrote 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/ghabix/spinecodex/pushing-ci-changes)<a href="https://agentmods.dev/skills/ghabix/spinecodex/pushing-ci-changes"><img src="https://agentmods.dev/badge/skills/ghabix/spinecodex/pushing-ci-changes.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 | $0.00021 | $0.00176 |
| Opus 5 | $0.00010 | $0.00088 |
| Sonnet 5 | $0.00004 | $0.00035 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
pushing-ci-changes 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 4d 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 pushing-ci-changes — 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.
What it actually says
The Codex repository prevents anyone from uploading changes to its CI configuration unless they've been granted a temporary role.
In order to push changes to .github/**/*.yml and related files you'll need the user to read
go/workflow-approvals and request an approval through that flow. It is not possible for you to
make progress by requesting an exemption yourself.
If you know you're about to push changes that would fail due to these restrictions you should still try to push anyways to confirm the user's account doesn't already have the necessary approval.
If you encounter a failed push due to these restrictions, share the go/workflow-approvals link with the user and ask them to return control to you once the approval has propagated to GitHub.
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.
- 4d ago First seen · 18 lines · 21 tokens per session scan A 1e5d0e3260f1
pushing-ci-changes is a skill published in the GitHub repository GhabiX/SpineCodex (126 stars, last pushed 8d ago), licensed Apache-2.0. It adds 21 tokens to every session and 176 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to pushing-ci-changes, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
securing-cloud-and-supply-chain
云原生与软件供应链安全防御。容器/K8s 加固、Service Mesh、CI/CD 安全、SLSA/SBOM/Sigstore、云 IAM、Secrets 管理、IaC 安全。Use when hardening Kubernetes clusters, auditing CI/CD pipelines, implementing supply chain security, managing cloud IAM, or reviewing IaC code.
automating-devops
DevOps knowledge reference covering Git workflows, testing strategies, DevSecOps, release pipeline orchestration (release.yml, multi-arch images, cosign integration), CI/CD pipelines, database management, observability, and performance optimization. Use when working with Git, CI/CD, release pipelines, ghcr image…
provisioning-infrastructure
Cloud-native infrastructure knowledge reference covering Kubernetes, Helm, Kustomize, Operators, CRDs, GitOps (ArgoCD, Flux), and IaC (Terraform, Pulumi, CDK). Use when provisioning infrastructure, managing clusters, or working with GitOps workflows.
tfx-ship
Skill "tfx-ship" from tellang/triflux, covering tfx-ship — triflux 릴리즈 자동화, 배포 채널 (3개 현행 + 1개 future), 전제 조건, 기본 경로 — ci 릴리즈 (권장) and 권장 실행 — release.yml 디스패치.
verification-and-release
Build a risk-based verification strategy and decide whether an integrated change is ready to release from traceable test, CI, coverage, operational, security, compatibility, and rollback evidence. Use when the question is what must be proven or whether a completed change can ship. Do not use to implement the feature…
CI/CD Pipeline Design
Stage isolation, caching, secret injection, artifact promotion, and rollback strategy for CI/CD pipelines.