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 skills add zircote-plugins/sdlc-quality --skill observabilitygit clone --depth 1 https://github.com/zircote-plugins/sdlc-qualityWrote 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/skills/zircote-plugins/sdlc-quality/observability)<a href="https://agentmods.dev/skills/zircote-plugins/sdlc-quality/observability"><img src="https://agentmods.dev/badge/skills/zircote-plugins/sdlc-quality/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.
<a href="https://agentmods.dev/skills/zircote-plugins/sdlc-quality/observability"><img src="https://agentmods.dev/badge/skills/zircote-plugins/sdlc-quality/observability.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00066 | $0.01810 |
| Opus 5.5 | $0.00026 | $0.00724 |
| Sonnet 5.5 | $0.00013 | $0.00362 |
| Haiku 4.5 | $0.00007 | $0.00181 |
Grade A, and why
observability scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:8080/health | jq . How it starts
The opening of the file, as written. The whole thing — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Observability Standards
Guidance for implementing observability requirements including logging, metrics, tracing, and monitoring configuration.
Tooling
Available Tools: If using Claude Code, the
agents:sre-engineeragent specializes in observability setup and SLO management. Theagents:devops-engineeragent can help configure monitoring infrastructure.
Logging Requirements
Structured Logging (MUST)
All logging MUST use structured format (JSON preferred):
{
"timestamp": "2024-01-15T10:30:00.000Z",
"level": "info",
"message": "Request processed",
"service": "api-gateway",
"trace_id": "abc123",
"span_id": "def456",
"duration_ms": 45,
"status_code": 200
}
Log Levels (MUST)
Use consistent log levels with defined semantics:
| Level | Purpose | When to Use |
|---|---|---|
| ERROR | Errors requiring attention | Failures, exceptions |
| WARN | Potential issues | Degraded performance, retries |
| INFO | Significant events | Request completion, state changes |
| DEBUG | Detailed information | Development, troubleshooting |
| TRACE | Very detailed tracing | Deep debugging |
Required Log Fields (MUST)
All log entries MUST include:
| Field | Description |
|---|---|
timestamp |
ISO 8601 format with timezone |
level |
Log severity level |
message |
Human-readable description |
service |
Service/application name |
Recommended Log Fields (SHOULD)
Log entries SHOULD include when applicable:
| Field | Description |
|---|---|
trace_id |
Distributed trace identifier |
span_id |
Span identifier |
user_id |
User identifier (if authenticated) |
request_id |
Request correlation ID |
duration_ms |
Operation duration |
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.
- 1mo ago First seen · 307 lines · 66 tokens per session scan A 0449aa8311f8
observability is a skill published in the GitHub repository zircote-plugins/sdlc-quality (11 stars, last pushed 27d ago), licensed MIT. It adds 66 tokens to every session and 1,810 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
setup
Interactive project setup from the ai-project-template — replaces the static SETUPGUIDE.md with a guided, multi-step workflow.
template-guide
Navigate template conventions, audit compliance, and guide upgrades for ai-project-template repos.
cut-release
Cut a clean release — bump versions across all files, update changelog, create GitHub release.
merge-to-main
Babysit a PR through CI — create, monitor, fix failures, merge when green.
sota-devsecops
State-of-the-art DevSecOps and software supply chain security (2026). Applies when building or auditing CI/CD pipelines, GitHub Actions workflows, supply chain controls, SBOM generation, SAST/secret-scanning gates, dependency management, container builds, container/artifact registries, IaC (Terraform), GitOps…
repo-scaffold
Scaffold or standardize a production-ready repository structure with specs, source layout, tests, CI, agent context, config examples, release notes, and operational docs. Use when starting a new repo, turning a prototype into a maintainable project, adding missing repository foundations, or creating a repo skeleton…