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.
git clone --depth 1 https://github.com/Amey-Thakur/AI-SKILLSWrote 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/amey-thakur/ai-skills/design-observability)<a href="https://agentmods.dev/commands/amey-thakur/ai-skills/design-observability"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/design-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/commands/amey-thakur/ai-skills/design-observability"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/design-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.00023 | $0.00258 |
| Opus 5 | $0.00012 | $0.00129 |
| Sonnet 5 | $0.00005 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
design-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 8d 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.
What it actually says
You were invoked as a slash command. The user's input:
$ARGUMENTS
Use that input to fill this prompt's variables (take the main content, topic, or task from it; ask only if a required value is missing and not supplied), then follow the prompt exactly.
Design observability for:
{service}
Concerns: {concerns}
Use the observability, metrics-instrumentation, structured-logging, and distributed-tracing skills.
Specify:
- The handful of metrics that describe user-facing health.
- What to log, at what level, with which fields for correlation.
- Where traces are needed and what spans matter.
- The alerts, each tied to a symptom users would notice.
- What you deliberately do not instrument, and why.
Rules: alert on symptoms rather than causes. Every alert needs a runbook and an action; if there is no action, it is a dashboard rather than an alert. Keep the metric set small enough to remember. Do not log personal data or secrets. State the cost implication of high-cardinality labels.
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.
- 8d ago First seen · 37 lines · 23 tokens per session scan A 2afdfc074c4d
design-observability is a command published in the GitHub repository Amey-Thakur/AI-SKILLS (7 stars, last pushed 5d ago), licensed MIT. It adds 23 tokens to every session and 258 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-09-03.
Other commands, from other repositories
fit-check
Audit a design or subsystem for primitive/problem fit (the wrong-primitive trap). Runs the architecture-fit-check skill.
perf-audit
Profile a performance complaint and fix the biggest contributor with Instruments and MetricKit.
swift6-fix
Diagnose and fix Swift 6 strict concurrency, Sendable, or MainActor isolation errors.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.