observability

observability is a skill for Claude Code from akaszubski/autonomous-dev. It costs 72 tokens per session (2,536 once invoked), scanned A, original, no licence file.

A set of techniques for understanding and monitoring program behavior, including structured logs, debuggers, profilers, and performance measurements. A profiler shows where a program spends time.

In plain words
What is it for?
Use it to add logging, inspect failures with pdb or ipdb, profile Python code, or monitor performance and metrics.
Why use it?
It helps locate errors, slow code, and useful diagnostic information.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the autonomous-dev plugin — 29 skills, 25 commands, 17 agents shipped together

Good fit Use it to add logging, inspect failures with pdb or ipdb, profile Python code, or monitor performance and metrics.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/akaszubski/autonomous-dev/observability
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.

Any agent
npx skills add akaszubski/autonomous-dev --skill observability
Clone the repo
git clone --depth 1 https://github.com/akaszubski/autonomous-dev

Made for: Claude Code.

Or install autonomous-dev, the plugin that ships this one along with the rest of its 29 skills, 25 commands, 17 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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/akaszubski/autonomous-dev/observability"><img src="https://agentmods.dev/badge/skills/akaszubski/autonomous-dev/observability.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,536 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 unknown 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.00072 $0.02536
Opus 5.5 $0.00029 $0.01014
Sonnet 5.5 $0.00014 $0.00507
Haiku 4.5 $0.00007 $0.00254

Measured 1mo ago against content hash 4f88880f4bab, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

plugins/autonomous-dev/skills/observability/SKILL.md · 357 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 1mo ago First seen · 357 lines · 72 tokens per session scan A 4f88880f4bab

Subscribe to this mod's changes

observability is a skill published in the GitHub repository akaszubski/autonomous-dev (34 stars, last pushed 23d ago), with no licence file. It adds 72 tokens to every session and 2,536 once invoked, about $0.0003 per session on Opus 5.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-09-03.

Related

Other skills, from other repositories

ai-development-guide

Applies language-agnostic and backend technical decision criteria, anti-pattern detection, debugging, and quality gates. Use when reviewing general/backend implementation choices, code smells, failures, or implementation completeness.

shinpr/claude-code-workflows · 43 tokens

recipe-diagnose

Investigate problem, verify findings, and derive solutions.

shinpr/claude-code-workflows · 15 tokens

root-cause

Find the mechanism behind a failure instead of patching its symptom - reproduce first, one variable per experiment with the prediction written before the run, exit by naming the mechanism and pinning it with a failing test. Use for a bug, an unexplained red test, or a failure that will not reproduce.

jjanczur/tyran · 61 tokens

logic-review

Find logic bugs in a single file or function via semi-formal execution tracing (Premises → Trace → Divergence → Trigger → Remedy). Trigger when a user shares code and suspects something is wrong without naming a concrete failure — phrases like "review this", "does this look right", "check this function", "audit this…

hyhmrright/logic-lens · 161 tokens

debug

Systematic bug investigation with a five-phase framework: reproduce, narrow, diagnose, fix, verify. Supports automated regression bisect via --regression flag. Produces a structured debug report with root cause analysis, regression test, and CQ/Q self-evaluations.

greglas75/zuvo · 55 tokens

logic-fix-all

Autonomous repository-wide audit-and-fix pipeline: health → review → locate/explain → fix → diff-verify → iterate until clean. Starts with a mandatory consent prompt (token-intensive); after consent runs hands-free. Trigger when the user wants ALL logic issues found and fixed — "fix everything", "fix all logic…

hyhmrright/logic-lens · 211 tokens