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-observe/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-observe)<a href="https://agentmods.dev/skills/acquiredl/acu/acu-observe"><img src="https://agentmods.dev/badge/skills/acquiredl/acu/acu-observe.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.00051 | $0.00825 |
| Opus 5 | $0.00026 | $0.00413 |
| Sonnet 5 | $0.00010 | $0.00165 |
| Haiku 4.5 | $0.00005 | $0.00082 |
Grade A, and why
acu-observe 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 8d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/acu-observe — Single-Pane Framework Observation
Aggregates 6 data streams into a 5-section report. Like /acu-pulse but broader — pulse is one data source, observe consumes all of them.
Protocol
Step 1: RUN — Execute observe.mjs
Run the observation script from the repository root:
node observe.mjs
Flags:
node observe.mjs --quick— one-line-per-section summary (5 lines total)node observe.mjs --section {name}— drill into one section with full detailnode observe.mjs --json— machine-readable output for all sections
Valid section names: health, pipelines, gates, review, roadmap
Step 2: INTERPRET — Analyze the output
The script produces five sections. Each aggregates a different set of data sources:
Section 1: Framework Health
Sources: _templates/tests/test.sh, pipeline .acu-meta.yaml files
- Template version + test results (pass/fail/warn counts)
- Pipeline version drift summary (N current / N outdated / N pre-versioning)
- Structural compliance (any pipelines missing gates, advance.sh, etc.)
Section 2: Pipeline Status
Sources: status.yaml across all pipelines
- Per-pipeline: name, active unit count, completion rate, current stage of most recent unit
- Stall alerts (units with no activity in 14+ days)
- Overall: total units, total complete, total active, total blocked
Section 3: Gate Performance
Sources: pulse.mjs gate analytics
- Autonomy rate (structural + full-stack)
- Top 5 lowest first-pass-rate gates (bottleneck spotlight)
- Failure ratio (structural vs semantic)
- Alert count by type (disagreement, stuck-input, error-loop, stall)
Section 4: Review Cycle
Sources: REVIEW-LOG.md
- Last review date
- Open suggestions count
- Open proposals count (
[PROPOSAL]entries with status "Awaiting approval") - One-off observation count
Section 5: Roadmap
Sources: _roadmap/ROADMAP.md, _roadmap/initiatives/*/status.yaml
- Active initiatives with item progress (N done / N total)
- Deferred items with reasons
- Recently completed initiatives
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.
- 8d ago First seen · 95 lines · 51 tokens per session scan A cc92c366453c
acu-observe is a skill published in the GitHub repository Acquiredl/Acu (2 stars, last pushed 29d ago), licensed MIT. It adds 51 tokens to every session and 825 once invoked, about $0.0003 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.