← ClaudeAtlas

foureyes-ledgerlisted

Report whether Astra is earning its keep. Reads the critique logs the seams write into consumer repos and shows, per seam, how often Astra was acted on versus factually wrong. Read-only, no model calls, no network. Takes repo paths: foureyes-ledger ~/dev/app-one ~/dev/app-two (default: the current repo).
Sultan1993/foureyes · ★ 0 · AI & Automation · score 72
Install: claude install-skill Sultan1993/foureyes
# foureyes-ledger — is Astra worth the five minutes? Every seam costs a `high`-effort Codex call, roughly five minutes. This is the only thing that says whether any of them earned it. ## Announce "Reading the Astra critique logs." ## Run it ```bash S=$(ls -d ~/.claude/plugins/cache/*/foureyes/*/scripts 2>/dev/null | sort -V | tail -1) node "$S/astra-ledger.mjs" <repo paths, or nothing for the list> # Astra: value and price node "$S/pipeline-stats.mjs" <repo paths, or nothing for cwd> # specs + dispatch history ``` Empty `S` is a broken install: STOP and say the plugin path did not resolve. Run **both** unless asked for one. They answer different questions from different sources, and only together do they cover the pipeline: | | source | needs | |---|---|---| | `astra-ledger` | critique logs the seams write | runs since the ledger shipped | | `pipeline-stats` | specs on disk (task sections) + `~/.claude/projects` transcripts | nothing — it is all retroactive | **With no arguments it reads `~/.claude/foureyes-repos`** — one path per line, `#` comments and `~` both fine — and falls back to the current directory if that file does not exist. The logs live in the repos you BUILD in, never in the plugin repo, so a bare run without that file reports on whatever you happen to be standing in. If the user asks about repos not in the list, add them there rather than passing paths every time. Each path may be a repo root, a specs directory, or an **umbrella holding sev