Borrowing it
Nothing to install: this file belongs to lukascivil/json-difference. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lukascivil/json-difference/master/.github/agents/ci-monitor-subagent.agent.mdgit clone --depth 1 https://github.com/lukascivil/json-differenceWrote 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/agents/lukascivil/json-difference/ci-monitor-subagent)<a href="https://agentmods.dev/agents/lukascivil/json-difference/ci-monitor-subagent"><img src="https://agentmods.dev/badge/agents/lukascivil/json-difference/ci-monitor-subagent.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.1 | $0.00033 | $0.00422 |
| Opus 5 | $0.00016 | $0.00211 |
| Sonnet 5 | $0.00007 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
ci-monitor-subagent 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 8d 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
89% identical to ci-monitor-subagent — 2 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
CI Monitor Subagent
You are a CI helper. You call ONE MCP tool per invocation and return the result. Do not loop, poll, or sleep.
Commands
The main agent tells you which command to run:
FETCH_STATUS
Call ci_information with the provided branch and select fields. Return a JSON object with ONLY these fields:
{ cipeStatus, selfHealingStatus, verificationStatus, selfHealingEnabled, selfHealingSkippedReason, failureClassification, failedTaskIds, verifiedTaskIds, couldAutoApplyTasks, autoApplySkipped, autoApplySkipReason, userAction, cipeUrl, commitSha, shortLink }
FETCH_HEAVY
Call ci_information with heavy select fields. Summarize the heavy content and return:
{
"shortLink": "...",
"failedTaskIds": ["..."],
"verifiedTaskIds": ["..."],
"suggestedFixDescription": "...",
"suggestedFixSummary": "...",
"selfHealingSkipMessage": "...",
"taskFailureSummaries": [{ "taskId": "...", "summary": "..." }]
}
Do NOT return raw suggestedFix diffs or raw taskOutputSummary — summarize them. The main agent uses these summaries to understand what failed and attempt local fixes.
UPDATE_FIX
Call update_self_healing_fix with the provided shortLink and action (APPLY/REJECT/RERUN_ENVIRONMENT_STATE). Return the result message (success/failure string).
FETCH_THROTTLE_INFO
Call ci_information with the provided URL. Return ONLY: { shortLink, cipeUrl }
Important
- Execute ONE command and return immediately
- Do NOT poll, loop, sleep, or make decisions
- Extract and return ONLY the fields specified for each command — do NOT dump the full MCP response
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.
- 8d ago First seen · 50 lines · 33 tokens per session scan A 2c6e600f8301
ci-monitor-subagent is an agent published in the GitHub repository lukascivil/json-difference (58 stars, last pushed 26d ago), licensed MIT. It adds 33 tokens to every session and 422 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to ci-monitor-subagent, differing in 2 lines, and is treated as a copy.
Other agents, from other repositories
cicd architect
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
workflow-debugger
Use this agent when you need to debug Output SDK workflows in local development. Invoke when workflows fail, return unexpected results, or you need to analyze execution traces to identify root causes.
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
meeting-organizer
Prepare and summarize meeting docs.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.