mantishack: Skill for Codex

.codex/skills/pushing-ci-changes/SKILL.md

pushing-ci-changes is a skill for Codex from deonmenezes/mantishack. It costs 21 tokens per session (176 once invoked), scanned A, original, Apache-2.0.

A guide for pushing changes to GitHub Actions, the service that runs automated checks and workflows for a GitHub repository. It explains how to handle rejected pushes and required temporary approval.

In plain words
What is it for?
Use it when pushing changes under .github or related CI files. It covers checking whether approval is needed and directing the user to the workflow-approvals process.
Why use it?
Some repositories block uploads that change CI configuration files, such as workflow YAML files. This explains the approval process instead of leaving the developer to guess why the push failed.

Skill for Codex

Written for Codex: installed under .codex/. Also seen: mentions Codex.

This is deonmenezes/mantishack's own configuration. It tells Codex how to work on mantishack itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mantishack configures →

Reuse

Borrowing it

Nothing to install: this file belongs to deonmenezes/mantishack. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/deonmenezes/mantishack/main/.codex/skills/pushing-ci-changes/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/deonmenezes/mantishack

Made for: Codex.

Wrote 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.

agentmods badge for pushing-ci-changes

README.md
[![agentmods](https://agentmods.dev/badge/skills/deonmenezes/mantishack/pushing-ci-changes/github.svg)](https://agentmods.dev/skills/deonmenezes/mantishack/pushing-ci-changes)
Your own site
<a href="https://agentmods.dev/skills/deonmenezes/mantishack/pushing-ci-changes"><img src="https://agentmods.dev/badge/skills/deonmenezes/mantishack/pushing-ci-changes/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.

agentmods 80×15 button for pushing-ci-changes

Your own site · 80×15
<a href="https://agentmods.dev/skills/deonmenezes/mantishack/pushing-ci-changes"><img src="https://agentmods.dev/badge/skills/deonmenezes/mantishack/pushing-ci-changes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 176 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.00176
Opus 5.5 $0.00008 $0.00070
Sonnet 5.5 $0.00004 $0.00035
Haiku 4.5 $0.00002 $0.00018

Measured 2mo ago against content hash 1e5d0e3260f1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.codex/skills/pushing-ci-changes/SKILL.md · 18 lines

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.

Changes

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.

  1. 2mo ago First seen · 18 lines · 21 tokens per session scan A 1e5d0e3260f1

Subscribe to this mod's changes

pushing-ci-changes is a skill published in the GitHub repository deonmenezes/mantishack (505 stars, last pushed 27d ago), licensed Apache-2.0. It adds 21 tokens to every session and 176 once invoked, about $0.0001 per session on Opus 5.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.