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/srstomp/pokayokay/observegit clone --depth 1 https://github.com/srstomp/pokayokayWrote 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/srstomp/pokayokay/observe)<a href="https://agentmods.dev/commands/srstomp/pokayokay/observe"><img src="https://agentmods.dev/badge/commands/srstomp/pokayokay/observe.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.00007 | $0.01098 |
| Opus 5 | $0.00003 | $0.00549 |
| Sonnet 5 | $0.00001 | $0.00220 |
| Haiku 4.5 | $0.00001 | $0.00110 |
Grade A, and why
observe 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 5d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Observability Workflow
Add observability for: $ARGUMENTS
Mode Detection
Parse $ARGUMENTS to determine mode:
--auditflag present → Observability gap analysis mode (creates tasks for gaps)- No flag → Design/implement mode (default behavior)
Steps
1. Identify Observability Need
From $ARGUMENTS, determine:
- Logging: Structured logs for debugging
- Metrics: Numerical measurements for monitoring
- Tracing: Request flow across services
- Alerting: Notifications for issues
2. Assess Current State
Check existing setup:
- Logging library (Pino, Winston, console)
- Metrics system (Prometheus, DataDog, CloudWatch)
- Tracing (OpenTelemetry, Jaeger)
- Alerting rules
3. Design Observability
For Logging:
- Define log levels (error, warn, info, debug)
- Structure log format (JSON)
- Add context (request ID, user ID)
- Configure log rotation
For Metrics:
- Identify key metrics (latency, throughput, errors)
- Define SLIs/SLOs
- Set up dashboards
- Configure retention
For Tracing:
- Instrument entry points
- Propagate context
- Add span attributes
- Configure sampling
For Alerting:
- Define alert conditions
- Set thresholds
- Configure notification channels
- Design escalation
4. Create Implementation Tasks
npx @stevestomp/ohno-cli create "Observability: [specific task]" -t chore
Audit Mode (--audit flag)
When --audit is specified, switch to observability gap analysis mode:
Audit Steps
- Inventory Current Observability Scan codebase for:
- Logging statements and configuration
- Metrics instrumentation
- Tracing setup
- Alerting rules
- Map Critical Paths Identify components that MUST have observability:
- API endpoints (latency, errors, throughput)
- Database operations (query time, connection pool)
- External service calls (availability, latency)
- Authentication flows (attempts, failures)
- Payment/transaction flows (success rate, failures)
- Identify Gaps by Environment
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.
- 5d ago First seen · 159 lines · 7 tokens per session scan A c72182e16799
observe is a command published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 2mo ago), licensed MIT. It adds 7 tokens to every session and 1,098 once invoked, about $0.0000 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
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.