ci-log-capture

A fixed action that downloads the failed part of a GitHub Actions run and stores it as a file artifact.

In plain words
What is it for?
It retrieves failed CI logs with the GitHub CLI, writes them to failed.log, and makes that file available to a later diagnostic step.
Why use it?
Saving the exact log makes later diagnosis repeatable and avoids fetching the same multi-megabyte log again.

Agent

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/watt-mind/factory/ci-log-capture
Clone the repo
git clone --depth 1 https://github.com/watt-mind/factory
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 148 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00148
Opus 5 $0.00000 $0.00074
Sonnet 5 $0.00000 $0.00030
Haiku 4.5 $0.00000 $0.00015

Measured 2d ago against content hash 64e2d3683366, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ci-log-capture 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 2d 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.

event-runtime/agents/ci-log-capture.md · 15 lines

What it actually says

ci-log-capture — closed-registry action

Not a prompt: this definition runs a fixed command template via the deterministic command adapter (lib/adapters/command.mjs). No model runs.

gh run view {runId} --repo {repo} --log-failed

The whole stream is captured to failed.log and declared as an artifact, so the worker stores it content-addressed. Downstream ci-doctor@2 reads those exact bytes instead of calling GitHub again: the diagnosis becomes reproducible and re-runnable offline, and a multi-megabyte log lives in the artifact store rather than blowing the inline-evidence limit.

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. 2d ago First seen · 15 lines · 0 tokens per session scan A 64e2d3683366

Subscribe to this mod's changes

ci-log-capture is an agent published in the GitHub repository watt-mind/factory (10 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 148 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-31.

Related

Other agents, from other repositories

ap-implementer

L3 executor - G4 IMPLEMENT. Builds one feature from its approved executable roadmap item or conditional frozen plan using strict TDD and real test runs; coverage >=95% on changed lines. Reports PLAN-CONFLICT rather than improvising.

Spielewoy/autoprompt-skill · 52 tokens

ap-manager

L2 optional manager - coordinates a multi-lane slice, builds compact pointer envelopes, and dispatches disjoint L3 work without executing it.

Spielewoy/autoprompt-skill · 32 tokens

ap-framework-generator

L3 executor - FRAMEWORK GENERATE. When the SELECTOR returns MISS, generates a one-off custom framework for the exact task shape - classifies the orthogonal axes, composes the gate sequence from the GATE-LIBRARY with the correct axis-specific gate, emits the gen- leaf with the BLOCKED invariant verbatim, binds an…

Spielewoy/autoprompt-skill · 93 tokens

ap-framework-validator

L4 terminal leaf - FRAMEWORK VALIDATE (HRN-5). A fresh, default-FAIL juror that proves a GENERATED framework is SOUND before any gate runs. Checks the HRN-5 default-FAIL checklist - every gate mapped, exactly one terminal DONE with negatives looping UP, the BLOCKED invariant verbatim, a non-empty acceptance set. PASS…

Spielewoy/autoprompt-skill · 93 tokens

ap-scope-coordinator

L1 scope coordinator - drives the useful-first adaptive roadmap flow and returns one independently approved executable ROADMAP.md before build.

Spielewoy/autoprompt-skill · 30 tokens

ap-juror

L4 terminal leaf - G7 SIGN-OFF. One independent sign-off panel seat that saw none of the intermediate work. Binary PASS/FAIL on opened evidence; default-FAIL. A FAIL naming a P0/P1 blocker is NOT arbitrable into PASS.

Spielewoy/autoprompt-skill · 58 tokens