A read-only scanner that checks the structure and health of workflow pipelines against the current shared templates. It reports missing parts, old template versions, and rule violations without editing files.

Use it to scan all pipelines for metadata, required scripts, completion checks, directory conventions, and other structural requirements.

It shows which pipelines need attention while leaving the project unchanged.

acu-check — Skill for Claude Code by Acquiredl: A read-only scanner that checks the structure and health…

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 skills/acquiredl/acu/acu-check

Any agent

npx skills add Acquiredl/Acu --skill acu-check

Clone the repo

git clone --depth 1 https://github.com/Acquiredl/Acu

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/acquiredl/acu/acu-check.svg)](https://agentmods.dev/skills/acquiredl/acu/acu-check)

Your own site

<a href="https://agentmods.dev/skills/acquiredl/acu/acu-check"><img src="https://agentmods.dev/badge/skills/acquiredl/acu/acu-check.svg" alt="Measured on agentmods" height="20"></a>

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,894 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.

Model	Per session	Once invoked
Fable 5.1	$0.00040	$0.03894
Opus 5	$0.00020	$0.01947
Sonnet 5	$0.00008	$0.00779
Haiku 4.5	$0.00004	$0.00389

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

Security

Grade A, and why

acu-check 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 5d 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.

.claude/skills/acu-check/SKILL.md · 363 lines

How it starts

The opening of the file, as written. The whole thing — 363 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/acu-check — Pipeline Health Scanner

Read-only diagnostic skill. Scans all pipelines under pipelines/ and reports structural health relative to the current template set. Never modifies files.

Protocol

Step 1: READ — Load current version

Read _templates/VERSION to get the current template version string.
Read pipelines/CLAUDE.md to identify all pipeline directories.

Step 2: SCAN — For each pipeline, run all 22 checks

For each pipeline directory found under pipelines/:

Check 1: Metadata / Version

Does .acu-meta.yaml exist at the pipeline root?
- Yes: Does template_version match _templates/VERSION?
  - Match → [CURRENT] {version}
  - Mismatch → [OUTDATED] {old version} (current: {new version})
- No: [PRE-VERSIONING] — no metadata, generated before Phase 1

Check 2: `gates/advance.sh` exists

File present → [PASS]
File absent → [FAIL]

Check 3: Completion gate exists

At least one file matching gate-*-complete.sh in gates/ → [PASS] {filename}
None found → [FAIL]

Check 4: Stage directory convention

Count directories at pipeline root matching ^[0-9]+- pattern.
- 2 or more → [PASS] {N} dirs follow {N}-{Name}/ convention
- 1 → [WARN] only 1 stage dir found
- 0 → check if pipeline uses an alternative layout (e.g., playbooks/):
  - Alternative layout present → [WARN] uses non-standard layout ({dirname}/) — not {N}-{Name}/
  - Nothing → [FAIL] no stage directories found
Note: If .acu-meta.yaml contains stage-dir-naming in known_deviations, downgrade FAIL/WARN to a suppressed notice.

Check 5: `templates/intake.yaml` and `templates/status.yaml` exist

Both present → [PASS] intake.yaml, status.yaml present
One missing → [FAIL] missing {filename}
Both missing → [FAIL] templates/intake.yaml and templates/status.yaml not found

Check 6: Sample unit directory exists

Look for any directory matching 001-* or 001 pattern in the units directory (check posts/, recipes/, engagements/, or the first {N}-{Name}/ dir for a units subdir).
Found → [PASS] {relative-path}/
Not found → [WARN] no sample unit directory found

Read the full file on GitHub · 363 lines

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.

5d ago First seen · 363 lines · 40 tokens per session scan A decfb42a2d7f

Subscribe to this mod's changes

acu-check is a skill published in the GitHub repository Acquiredl/Acu (2 stars, last pushed 26d ago), licensed MIT. It adds 40 tokens to every session and 3,894 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.

CI and CD DevOps and cloud

import-prom-rule

Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…

ccfos/nightingale · 125 tokens

azsdk-common-pipeline-analysis

Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…

Azure/azure-sdk-for-net · 192 tokens

configure-env-variables

Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…

microsoft/power-platform-skills · 119 tokens

acu-check

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/acu-check — Pipeline Health Scanner

Protocol

Step 1: READ — Load current version

Step 2: SCAN — For each pipeline, run all 22 checks

Check 1: Metadata / Version

Check 2: `gates/advance.sh` exists

Check 3: Completion gate exists

Check 4: Stage directory convention

Check 5: `templates/intake.yaml` and `templates/status.yaml` exist

Check 6: Sample unit directory exists

What this file has done since we first saw it

Other skills, from other repositories

import-prom-rule

azsdk-common-pipeline-analysis

configure-env-variables

desktop-principles

atmos-cache

atmos-profiles

acu-check

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/acu-check — Pipeline Health Scanner

Protocol

Step 1: READ — Load current version

Step 2: SCAN — For each pipeline, run all 22 checks

Check 1: Metadata / Version

Check 2: gates/advance.sh exists

Check 3: Completion gate exists

Check 4: Stage directory convention

Check 5: templates/intake.yaml and templates/status.yaml exist

Check 6: Sample unit directory exists

What this file has done since we first saw it

Other skills, from other repositories

import-prom-rule

azsdk-common-pipeline-analysis

configure-env-variables

desktop-principles

atmos-cache

atmos-profiles

Check 2: `gates/advance.sh` exists

Check 5: `templates/intake.yaml` and `templates/status.yaml` exist