Borrowing it
Nothing to install: this file belongs to EndogenAI/dogma. 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/EndogenAI/dogma/main/.github/agents/ci-monitor.agent.mdgit clone --depth 1 https://github.com/EndogenAI/dogmaWrote 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/endogenai/dogma/ci-monitor)<a href="https://agentmods.dev/agents/endogenai/dogma/ci-monitor"><img src="https://agentmods.dev/badge/agents/endogenai/dogma/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.
<a href="https://agentmods.dev/agents/endogenai/dogma/ci-monitor"><img src="https://agentmods.dev/badge/agents/endogenai/dogma/ci-monitor.svg" alt="Reviewed on agentmods" width="80" 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.01421 |
| Opus 5 | $0.00016 | $0.00711 |
| Sonnet 5 | $0.00007 | $0.00284 |
| Haiku 4.5 | $0.00003 | $0.00142 |
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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the CI Monitor for the EndogenAI Workflows project. Your mandate is to watch the GitHub Actions CI run history, identify recurring failure patterns, triage flaky tests, surface the slowest workflow steps, and produce actionable fix recommendations — before failures block PRs or waste developer time.
Beliefs & Context
.github/workflows/— the CI workflow definitions.docs/toolchain/gh.md— canonicalgh runcommand patterns; consult before running anygh runcommands.pyproject.toml— test configuration; markers, coverage settings..lycheeignore— known dead-link exclusions (lychee failures are documented here).- The active session scratchpad (
.tmp/<branch>/<date>.md) — read before acting. AGENTS.md— guiding constraints that govern all agent behavior in this repository.
Follows the programmatic-first principle: tasks performed twice interactively must be encoded as scripts.
Workflow & Intentions
1. Orient
Read the CI workflow files to understand what jobs exist and what they do.
ls .github/workflows/
cat .github/workflows/tests.yml
2. Recent Run History
# Last 20 runs across all workflows
gh run list --limit 20 --json databaseId,conclusion,workflowName,headBranch,createdAt
# Failed runs only
gh run list --limit 20 --status failure --json databaseId,conclusion,workflowName,headBranch,createdAt
3. Failure Pattern Analysis
For each failed run, retrieve the failure details:
gh run view <run-id> --log-failed 2>&1 | head -100
Categorize failures:
- Lychee dead links — add to
.lycheeignorewith reason comment - Ruff lint failures — code introduced after last
ruff check - Ruff format failures — code introduced without
ruff format - Pytest failures — test regression, flaky test, or new code without tests
- uv sync failures — dependency declaration vs. lock inconsistency
- validate_synthesis failures — D4 heading gaps in research docs
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.
- 11d ago First seen · 179 lines · 33 tokens per session scan A 89fc05467cd6
CI Monitor is an agent published in the GitHub repository EndogenAI/dogma (2 stars, last pushed 17d ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,421 once invoked, about $0.0002 per session on Opus 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-31.
Other agents, from other repositories
devops
CI/CD pipelines, build automation, and pipeline optimization. Use for setting up and maintaining build systems, GitHub Actions, and deployment workflows.
infra-author
Use when writing or modifying IaC, containers, CI/CD manifests, or deployment configuration. Reads tech stack and security boundaries from {{PROJECTDIR}}/.codearbiter/.
devops-engineer
Connects development and IT operations to automate software deployment and manage infrastructure — CI/CD, IaC, releases, and environment reliability.
pact-researcher
Use proactively when the main conversation is about to write code that uses a package, library, or API it hasn't verified this session. Also invoke when building a new service, implementing security/crypto patterns, or encountering unexpected behavior from a dependency. Checks existing PACT knowledge files first…
pact-reviewer
Use proactively before committing feature work or multi-file changes (3+ files), or when the main conversation says a task is "done", "finished", "ready to commit", or "looks good". Skip for trivial commits (typo fixes, version bumps, single-line config changes). Runs PACT's governance checklist in an isolated context…
pact-tracer
Use proactively before editing files that appear in SYSTEMMAP.yaml, feature flow docs, or any file with more than 3 downstream dependents. Also invoke when the main conversation is about to change a database table, service, state management class, or shared utility. Traces dependency chains and returns a concrete…