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 skills/tomzx/agents/create-observabilitynpx skills add tomzx/agents --skill create-observabilitygit clone --depth 1 https://github.com/tomzx/agentsWhat 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.00028 | $0.01633 |
| Opus 5 | $0.00014 | $0.00816 |
| Sonnet 5 | $0.00006 | $0.00327 |
| Haiku 4.5 | $0.00003 | $0.00163 |
Grade A, and why
create-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 2d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Observability
Defines how a feature's production health will be monitored by identifying log statements, service metrics, distributed traces, and alerts before implementation begins.
Without this step, features ship blind: outages go undetected, root causes take hours to find, and on-call engineers lack runbooks.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. - If no argument is provided, locate the feature directory under
.sdlc/features/whose frontmatterissuefield references$ISSUE_NUMBER. .sdlc/features/N-<slug>/specification.md(must have passed review with findings verdictapproved), or a specification document provided in context or as a file path ($1).sdlc/features/N-<slug>/lifecycle.md(optional, if a lifecycle document was produced): monitor state transitions, invariant violations, and retention cleanup as part of observability.sdlc/features/N-<slug>/telemetry.md(optional, if a telemetry plan was produced): align observability with business metrics already defined.sdlc/features/N-<slug>/requirements.md(optional, for cross-referencing NFRs like latency and availability targets)
Steps
- Read the specification, lifecycle document (if present), telemetry plan (if present), and requirements.
- Identify the critical paths and failure modes from the specification.
- For each critical path, determine what log entries are needed for debugging.
- Define service-level metrics (counters, histograms, gauges) that reflect system health.
- Identify where distributed traces should be emitted for cross-service flows.
- Define health checks and readiness probes for new services or endpoints.
- Specify alerts with clear conditions, severity, and runbook links. When the monitoring stack is Prometheus-compatible, write the normative alert definitions to
.sdlc/features/N-<slug>/alerts.yaml(Prometheus rule format, template atskills/sdlc/templates/features/alerts.yaml) and keep the per-alert tables in the document as the human-readable summary. Validate best-effort withpromtool check rules alerts.yamlwhen available; a missing tool is skipped, a validation failure is a defect to fix before handoff. - Determine observability infrastructure requirements (existing vs. new instrumentation).
- Write the output to
.sdlc/features/N-<slug>/observability.md(plusalerts.yamlwhen alerts are defined and the stack is Prometheus-compatible).
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.
- 2d ago First seen · 120 lines · 28 tokens per session scan A d80f03f6a62c
create-observability is a skill published in the GitHub repository tomzx/agents (5 stars, last pushed 5d ago), licensed MIT. It adds 28 tokens to every session and 1,633 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.