Borrowing it
Nothing to install: this file belongs to Acquiredl/Acu. 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/Acquiredl/Acu/master/.claude/skills/acu-pulse/SKILL.mdgit clone --depth 1 https://github.com/Acquiredl/AcuWrote 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/skills/acquiredl/acu/acu-pulse)<a href="https://agentmods.dev/skills/acquiredl/acu/acu-pulse"><img src="https://agentmods.dev/badge/skills/acquiredl/acu/acu-pulse.svg" alt="Measured on agentmods" 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.00040 | $0.00802 |
| Opus 5 | $0.00020 | $0.00401 |
| Sonnet 5 | $0.00008 | $0.00160 |
| Haiku 4.5 | $0.00004 | $0.00080 |
Grade A, and why
acu-pulse 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 6d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/acu-pulse — Pipeline Health Metrics
Read-only diagnostic skill. Computes autonomy rate, gate pass rates, cycle times, and pattern alerts from audit logs across all pipelines.
Protocol
Step 1: RUN — Execute pulse.mjs
Run the metrics script from the repository root:
node pulse.mjs
If the user asks for machine-readable output, use node pulse.mjs --json instead.
If the user only wants alerts, use node pulse.mjs --alerts.
Step 2: INTERPRET — Analyze the output
The script produces five sections. Interpret each:
Unit Classifications
Each work unit is classified by its audit history:
| Class | Meaning |
|---|---|
| CLEAN | Zero structural failures |
| NEAR-CLEAN | One structural failure (resolved) |
| TROUBLED | Two or more structural failures |
| BLOCKED | Currently stuck — last gate result is FAIL |
Autonomy Rate
Percentage of completed units that ran clean with zero human intervention. Only completed units count. Bug-induced units are excluded (they pollute the signal).
Gate Pass Rates
Cross-pipeline pass/fail ratio per gate type. Low-rate gates are bottlenecks — they may indicate unclear specs, overly strict checks, or systemic quality issues at that stage transition.
Alerts
[STALL]— No gate transition in 14+ days. Unit may be abandoned or blocked.
Cycle Times
Wall-clock duration per stage from status.yaml timestamps. Useful for identifying stages that take disproportionately long, but note these include idle time (not active work time).
Gate Analytics
Deep metrics on gate performance:
- First-pass rate — percentage of units that pass each gate on their first attempt. Lower rates indicate unclear specs or overly strict exit criteria.
- Retry times — average wall-clock time between a gate failure and the next attempt.
- Top failure causes — most common structural check failures across pipelines.
Pipeline Metrics
Per-pipeline health indicators:
- Completion rate — units reaching final stage vs total created. Low rates indicate systemic stalls.
- Stage velocity — average/min/max time per stage type across all pipelines. Identifies slow stages.
- Stall detection — units with no gate transition in 14+ days. Surfaced as
[STALL]alerts.
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.
- 6d ago First seen · 102 lines · 40 tokens per session scan A 5a08d1ca3221
acu-pulse is a skill published in the GitHub repository Acquiredl/Acu (2 stars, last pushed 27d ago), licensed MIT. It adds 40 tokens to every session and 802 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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.
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…
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…