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.
npx agentmods add commands/sefaertunc/worclaude/observabilitygit clone --depth 1 https://github.com/sefaertunc/WorclaudeWrote 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/commands/sefaertunc/worclaude/observability)<a href="https://agentmods.dev/commands/sefaertunc/worclaude/observability"><img src="https://agentmods.dev/badge/commands/sefaertunc/worclaude/observability.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 | $0.00012 | $0.00537 |
| Opus 5 | $0.00006 | $0.00269 |
| Sonnet 5 | $0.00002 | $0.00107 |
| Haiku 4.5 | $0.00001 | $0.00054 |
Grade A, and why
observability 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 4d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Surface the local observability report for this project. The data lives in
.claude/observability/ and is captured by hooks that fire on Claude Code's
InstructionsLoaded, UserPromptSubmit, and SubagentStart / SubagentStop
events. Zero data leaves the machine — the folder is gitignored.
Run
worclaude observability
The CLI reads the JSONL files (skill loads, command invocations, agent events), pairs agent start/stop events to compute durations, and emits a Markdown report covering:
- Top skills by load count, with last-seen timestamp.
- Top commands by invocation count.
- Agent invocations with completed/failed counts and average duration.
- Anomalies — installed skills that never loaded, agents that fail more often than they complete.
- Suggestions — skills not loaded in 30+ days (consider retiring).
Flags:
--json— emit the raw report object as JSON (machine-readable).--out <file>— write the report to a file instead of stdout.
Use cases
- Skill hygiene. Skills that never load are noise — either rename them
to match the prompts users actually type, update their description for
skill-hint.cjskeyword match, or retire them. - Agent reliability. If an agent's failure ratio is high, look at what
the agent is being asked to do. The
bug-fixerandverify-appagents should sit near 100% completion in a healthy project. - Command surface review. If
/some-commandhas zero invocations after weeks of use, it might not be earning its slot in the surface.
Privacy
The report is built entirely from local files. No network egress, no
upload, no opt-in dashboard. To disable capture entirely, set
WORCLAUDE_HOOK_PROFILE=minimal — the observability hooks short-circuit on
that profile (same as learn-capture and correction-detect).
To purge captured data, delete .claude/observability/. It will be
recreated empty on the next session start.
Trigger Phrases
- "show observability"
- "observability report"
- "what's my project's observability report?"
- "skill usage report"
- "agent reliability"
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.
- 4d ago First seen · 60 lines · 12 tokens per session scan A dd34b1808357
observability is a command published in the GitHub repository sefaertunc/Worclaude (4 stars, last pushed 25d ago), licensed MIT. It adds 12 tokens to every session and 537 once invoked, about $0.0001 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 commands, from other repositories
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
config
Command "config" from sdebruyn/fabric-dw-mcp-cli, covering configuration & defaults, http retry budget, sql retry budget, mcp workspace allowlist {#mcp-workspace-allowlist} and mcp server log level.
deps-age
Analyze dependency freshness and maintenance activity.
session-active
Set the persistent, per-session credo mode to active.