observability-crusade

observability-crusade is a command for Claude Code from btachinardi/church. It costs 30 tokens per session (4,040 once invoked), scanned A, original, MIT.

A command that checks a codebase’s observability: the logs, traces, measurements, and error handling that show what software is doing. It can inspect the whole project or selected API and web areas.

In plain words
What is it for?
Use it to survey logging and error-handling problems, or apply fixes with the illuminate option in a chosen directory or scope.
Why use it?
It helps reveal silent failures, unlogged requests, missing request tracking, and other gaps that make production problems difficult to investigate.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the church plugin — 1 skill, 14 commands, 14 agents shipped together

Good fit Use it to survey logging and error-handling problems, or apply fixes with the illuminate option in a chosen directory or scope.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/btachinardi/church/observability-crusade
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.

Clone the repo
git clone --depth 1 https://github.com/btachinardi/church

Made for: Claude Code.

Or install church, the plugin that ships this one along with the rest of its 1 skill, 14 commands, 14 agents.

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 observability-crusade

README.md
[![agentmods](https://agentmods.dev/badge/commands/btachinardi/church/observability-crusade/github.svg)](https://agentmods.dev/commands/btachinardi/church/observability-crusade)
Your own site
<a href="https://agentmods.dev/commands/btachinardi/church/observability-crusade"><img src="https://agentmods.dev/badge/commands/btachinardi/church/observability-crusade/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 observability-crusade

Your own site · 80×15
<a href="https://agentmods.dev/commands/btachinardi/church/observability-crusade"><img src="https://agentmods.dev/badge/commands/btachinardi/church/observability-crusade.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,040 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.00030 $0.04040
Opus 5 $0.00015 $0.02020
Sonnet 5 $0.00006 $0.00808
Haiku 4.5 $0.00003 $0.00404

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

Security

Grade A, and why

observability-crusade 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 10d 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.

commands/observability-crusade.md · 534 lines

How it starts

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

The Observability Crusade

"In the beginning, there was darkness upon the codebase. And the Observability Purists said: LET THERE BE LIGHT."

This command orchestrates a multi-squad crusade to eliminate observability sins and bring full instrumentation to your codebase.

Command Invocation

# Survey darkness only (report mode)
/observability-crusade

# Survey specific scope
/observability-crusade --scope api
/observability-crusade --scope web

# Survey and apply fixes
/observability-crusade --illuminate

# Target specific directory
/observability-crusade apps/api/src/domains/orders
/observability-crusade apps/api/src/domains/orders --illuminate

The Four Phases

Phase 1: The Darkness Survey

First, we scan the codebase to identify every sin against observability:

Sins to detect:

  1. Empty Catch Blocks: catch (e) {}, catch {}, catch blocks with only comments
  2. Bare Console Calls: console.log, console.error, console.warn in non-test files
  3. Untraced Endpoints: API controllers/routes with no logging
  4. Untraced External Calls: HTTP calls, database queries without timing/logging
  5. Missing Correlation IDs: No middleware, no propagation
  6. Unstructured Logs: String concatenation instead of structured objects
  7. Missing Health Checks: No /health endpoint
  8. Swallowed Errors: Catch and return null/undefined without logging
  9. Missing Business Metrics: No counters or histograms for business operations
  10. Error Responses Without Context: Throwing exceptions without logging details

Scan commands:

# Empty catch blocks
rg 'catch\s*\([^)]*\)\s*\{\s*\}' --type ts --type tsx

# Bare console calls (exclude test files)
rg 'console\.(log|error|warn|info|debug)' --type ts --type tsx -g '!*.spec.ts' -g '!*.test.ts' -g '!*.e2e.ts'

# Catch blocks with only comments
rg 'catch.*\{[^}]*//[^}]*\}' --type ts --type tsx

# Missing correlation ID usage in services
rg 'logger\.(info|error|warn)' -A 2 --type ts | rg -v 'correlationId'

# Unstructured string concat logs
rg "logger\.(info|error|warn)\(['\"].*\+.*\)" --type ts

# Missing health check endpoints
rg -L '@Get.*health' apps/api

# Promise without catch
rg 'await\s+\w+\(.*\)' --type ts -g '!*.spec.ts' | rg -v 'try|catch'

Read the full file on GitHub · 534 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.

  1. 10d ago First seen · 534 lines · 0 tokens per session scan A d50c7db3c438

Subscribe to this mod's changes

observability-crusade is a command published in the GitHub repository btachinardi/church (58 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 4,040 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-30.