monitor-ci skillA
monitor-ci is agent-read markdown (skill) from max-sixty/tend: Poll CI to a terminal result. Use after any push you are accountable for, and before calling a failure pre-existing..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Monitoring CI after a push After pushing, what to do depends on whether a red result creates a follow-up. **A pushed fix is always gated** (triage fix, CI fix, requested change): you own its CI, so don't pre-judge a fresh push as ungated — no other tend run fixes a PR branch's CI (`tend-ci-fix` watches only the default branch). Approving a PR is also gated: dismiss it on red. **Nothing gated** (review-only, a reply, a no-op): end, stating anything still in flight. Don't background-poll — the completion notification isn't reliably delivered to a CI session. ## Required skills - Load `/tend-ci-runner:dismiss-approval` if an approved PR turns red. - Load `/tend-ci-runner:fix-a-bug` and `/tend-ci-runner:push-commits` before fixing and pushing a red check. - Load `/tend-ci-runner:post-to-github` before composing a comment about unaddressed findings. ## Poll the pinned commit Poll with the bundled script, pinned to the commit this session is accountable for — never the PR's current head: another actor can advance the head while the loop sleeps, and a poll that follows it reports *their* commit's results as yours: ```bash # After your own push: PINNED_SHA=$(git rev-parse HEAD) …
Read the whole file at its exact version.
How to install
mdr add max-sixty/tend/monitor-ci@git:20260924.b3c4ba6mdr add max-sixty/tend/monitor-ci@sha256:23ecb0e8c4956273Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_5kcy2jzn5b2mewbe)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260924.b3c4ba6 latest | 2026-09-24 | b3c4ba6 | 6,414 B | A | view · diff |
| git:20260923.f93552f | 2026-09-23 | f93552f | 6,091 B | A | view · diff |
| git:20260922.ffd3fb6 | 2026-09-22 | ffd3fb6 | 6,075 B | A | view · diff |
| git:20260922.1a48bb0 | 2026-09-22 | 1a48bb0 | 5,412 B | A | view · diff |
| git:20260918.1ca04b2 | 2026-09-18 | 1ca04b2 | 5,504 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6414 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
max-sixty/tend · 39 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5kcy2jzn5b2mewbe GET https://markdownregistry.com/api/v1/resolve?ref=max-sixty/tend/monitor-ci GET https://markdownregistry.com/api/v1/blob/23ecb0e8c4956273c1d011c18360a8969d8c321dfe14cde81285d805049054c4
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.