Coherence-Network: Skill for Claude Code

.cursor/skills/pipeline-monitor/SKILL.md

pipeline-monitor is a skill for Claude Code, Cursor from seeker71/Coherence-Network. It costs 36 tokens per session (324 once invoked), scanned A, original, Apache-2.0.

A checker for the Coherence Network’s task pipeline, which is the sequence of work items moving from idea to completion. It reports stalled work, failing providers, timeouts, and notable progress.

In plain words
What is it for?
Use it to inspect pipeline health on demand, on a schedule, through Telegram, or as an OpenClaw health check.
Why use it?
It helps find work that has stopped or failed without useful diagnostic information. It also highlights recoveries, strong success runs, and ideas reaching validation.

Skill for Claude CodeCursor

Written for Claude Code and Cursor: allowed-tools in frontmatter, but also installed under .cursor/. Also seen: built for openclaw.

This is seeker71/Coherence-Network's own configuration. It tells Claude Code and Cursor how to work on Coherence-Network 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 Coherence-Network configures →

Reuse

Borrowing it

Nothing to install: this file belongs to seeker71/Coherence-Network. 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/seeker71/Coherence-Network/main/.cursor/skills/pipeline-monitor/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/seeker71/Coherence-Network

Made for: Claude Code, Cursor.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/seeker71/coherence-network/pipeline-monitor/github.svg)](https://agentmods.dev/skills/seeker71/coherence-network/pipeline-monitor)
Your own site
<a href="https://agentmods.dev/skills/seeker71/coherence-network/pipeline-monitor"><img src="https://agentmods.dev/badge/skills/seeker71/coherence-network/pipeline-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 pipeline-monitor

Your own site · 80×15
<a href="https://agentmods.dev/skills/seeker71/coherence-network/pipeline-monitor"><img src="https://agentmods.dev/badge/skills/seeker71/coherence-network/pipeline-monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 324 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.00036 $0.00324
Opus 5 $0.00018 $0.00162
Sonnet 5 $0.00007 $0.00065
Haiku 4.5 $0.00004 $0.00032

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

Security

Grade A, and why

pipeline-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.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/check_pipeline.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.cursor/skills/pipeline-monitor/SKILL.md · 43 lines

What it actually says

Pipeline Monitor

Check the Coherence Network task pipeline and report on:

  1. Blockers — anything stopping progress:

    • Tasks stuck in running for more than 10 minutes
    • Providers with 3+ consecutive failures (blocked by Thompson Sampling)
    • Ideas with all tasks failed and no pending retry
    • Blind timeouts (cost with zero diagnostic value)
  2. Remarkable events — noteworthy progress:

    • Ideas that advanced a phase (spec → impl → test → review → complete)
    • Provider success streaks (5+ consecutive successes)
    • New providers coming online or existing ones recovering
    • Batch completion rates above 90%
    • Ideas reaching validated manifestation status

How to run

python .cursor/skills/pipeline-monitor/scripts/check_pipeline.py

The script outputs a structured report suitable for Telegram or console display.

Integration

This skill can be run:

  • On demand: python .cursor/skills/pipeline-monitor/scripts/check_pipeline.py
  • On a schedule: pair with the local_runner --loop mode
  • Via Telegram: responds to /attention command
  • Via OpenClaw: as a periodic health check skill
Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 · 43 lines · 36 tokens per session scan A 84bc762f3fc3

Subscribe to this mod's changes

pipeline-monitor is a skill published in the GitHub repository seeker71/Coherence-Network (3 stars, last pushed 2d ago), licensed Apache-2.0. It adds 36 tokens to every session and 324 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens