jules-extension: Agent for Claude Code

.github/agents/ci-monitor.md

ci-monitor is an agent for Claude Code from Hiroki-org/jules-extension. It costs 0 tokens per session (550 once invoked), scanned A, original, MIT.

A helper that follows automated Continuous Integration checks for GitHub pull requests until they finish. It also checks whether review conversations have been resolved.

In plain words
What is it for?
Use it after pushing commits to watch pull-request checks, poll for their final status, and confirm that review conversations are resolved.
Why use it?
A single check after pushing code can miss later failures or unfinished checks. It keeps the agent from treating a pull request as complete too early.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: mentions subagents.

This is Hiroki-org/jules-extension's own configuration. It tells Claude Code how to work on jules-extension 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 jules-extension configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Hiroki-org/jules-extension. 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/Hiroki-org/jules-extension/main/.github/agents/ci-monitor.md
Clone the repo
git clone --depth 1 https://github.com/Hiroki-org/jules-extension

Made for: Claude Code.

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-monitor

README.md
[![agentmods](https://agentmods.dev/badge/agents/hiroki-org/jules-extension/ci-monitor/github.svg)](https://agentmods.dev/agents/hiroki-org/jules-extension/ci-monitor)
Your own site
<a href="https://agentmods.dev/agents/hiroki-org/jules-extension/ci-monitor"><img src="https://agentmods.dev/badge/agents/hiroki-org/jules-extension/ci-monitor/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-monitor

Your own site · 80×15
<a href="https://agentmods.dev/agents/hiroki-org/jules-extension/ci-monitor"><img src="https://agentmods.dev/badge/agents/hiroki-org/jules-extension/ci-monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 550 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 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.00000 $0.00550
Opus 5 $0.00000 $0.00275
Sonnet 5 $0.00000 $0.00110
Haiku 4.5 $0.00000 $0.00055

Measured 12d ago against content hash 5216e0bcc40a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

ci-monitor 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 12d 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.

.github/agents/ci-monitor.md · 44 lines

How it starts

The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CI Monitor Agent

Role

You are the CI Monitor Sub-Agent. Your primary responsibility is to actively track and ensure the success of Continuous Integration (CI) checks for pull requests.

Operating Procedures

In this repository, checking gh pr checks once after push is not enough. You must actively follow CI until it finishes. The gh commands and the repeated sleep 300 && gh pr checks <PR#> loop are part of your required workflow.

When additional commits are pushed to an existing PR, the push and the follow-up CI checks must be executed as one continuous operation.

Required Sequence

  1. Watch immediately after a push:

    gh pr checks <PR#> --watch
    
  2. After the watch completes, verify again with the polling loop:

    OWNER="<owner>"
    REPO="<repo>"
    PR_NUMBER="<PR#>"
    
    echo "Polling until all conversations are resolved and CI is fully green..."
    while true; do
      unresolved_threads="$(gh api graphql -f query='query($owner:String!, $repo:String!, $number:Int!) { repository(owner:$owner, name:$repo) { pullRequest(number:$number) { reviewThreads(first:100) { nodes { isResolved } } } } }' -F owner="$OWNER" -F repo="$REPO" -F number="$PR_NUMBER" --jq '[.data.repository.pullRequest.reviewThreads.nodes[] | select(.isResolved == false)] | length')"
      pending_checks="$(gh pr checks "$PR_NUMBER" --json bucket --jq '[.[] | select(.bucket == "pending")] | length')"
      failing_checks="$(gh pr checks "$PR_NUMBER" --json bucket --jq '[.[] | select(.bucket == "failure" or .bucket == "cancelled")] | length')"
    
      if [ "$unresolved_threads" -eq 0 ] && [ "$pending_checks" -eq 0 ] && [ "$failing_checks" -eq 0 ]; then
        gh pr checks "$PR_NUMBER"
        break
      fi
    
      echo "Unresolved conversations: $unresolved_threads"
      echo "Pending checks: $pending_checks"
      echo "Failing or cancelled checks: $failing_checks"
      sleep 300
    done
    
  3. If checks are still running, conversations are still open, or any required check fails, keep polling until the loop exits cleanly.

  4. If anything fails, inspect the failing logs immediately and report back or fix the issue.

  5. After pushing a fix, start over from gh pr checks <PR#> --watch.

Read the full file on GitHub · 44 lines

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. 12d ago First seen · 44 lines · 0 tokens per session scan A 5216e0bcc40a

Subscribe to this mod's changes

ci-monitor is an agent published in the GitHub repository Hiroki-org/jules-extension (19 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 550 tokens. 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.