claude_hooks: Skill for Claude Code

.agents/skills/ci-monitoring/SKILL.md

ci-monitoring is a skill for Claude Code, Codex from gabriel-dehan/claude_hooks. It costs 54 tokens per session (1,034 once invoked), scanned A, original, no licence file.

Instructions for waiting for GitHub Actions, GitHub’s automated build and test service, to finish on a pull request after pushing commits.

In plain words
What is it for?
Use them after pushing to a pull-request branch when you need to monitor its CI checks before reporting back or approving it.
Why use it?
They help you confirm whether automated checks passed without waiting forever or stopping too soon. This gives a clearer basis for reporting the result or approving the pull request.

Skill for Claude CodeCodex

Which agent this was written for is unclear — body not stored (licence); the path alone says nothing. Also seen: installed under .agents/ (shared by several agents).

This is gabriel-dehan/claude_hooks's own configuration. It tells Claude Code and Codex how to work on claude_hooks 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 claude_hooks configures →

Reuse

Borrowing it

Nothing to install: this file belongs to gabriel-dehan/claude_hooks. 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/gabriel-dehan/claude_hooks/main/.agents/skills/ci-monitoring/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/gabriel-dehan/claude_hooks

Made for: Claude Code, 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 ci-monitoring

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/gabriel-dehan/claude_hooks/ci-monitoring"><img src="https://agentmods.dev/badge/skills/gabriel-dehan/claude_hooks/ci-monitoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,034 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.
Origin unknown 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.00054 $0.01034
Opus 5.5 $0.00022 $0.00414
Sonnet 5.5 $0.00011 $0.00207
Haiku 4.5 $0.00005 $0.00103

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

Security

Grade A, and why

ci-monitoring 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.

.agents/skills/ci-monitoring/SKILL.md · 104 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on 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 · 104 lines · 54 tokens per session scan A ba30015f3511

Subscribe to this mod's changes

ci-monitoring is a skill published in the GitHub repository gabriel-dehan/claude_hooks (41 stars, last pushed 3d ago), with no licence file. It adds 54 tokens to every session and 1,034 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

Verification & Quality Assurance

Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.

ruvnet/ruflo · 36 tokens

quality-scan

Run a scoped, read-only quality scan and report exact-candidate evidence, failures and frozen debt. Use for an ad-hoc gate sweep or release preparation; a static scan is not full release acceptance.

diegosouzapw/OmniRoute · 45 tokens

e2e-testing

Use when reviewing CI coverage, automated checks, or test strategy related to Implement end-to-end testing. Focus on whether the rule is continuously verified, not just documented.

thedaviddias/Front-End-Checklist · 38 tokens

mirrord-prev-env

Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…

metalbear-co/mirrord · 122 tokens

test-setup

Scaffold the test framework and CI — tests/ directory, engine test runner, GitHub Actions workflow. Once, before the first sprint.

Donchitos/Claude-Code-Game-Studios · 32 tokens

ci

Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…

onsi/ginkgo · 151 tokens