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/morodomi/dev-crewWrote 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/agents/morodomi/dev-crew/observability-reviewer)<a href="https://agentmods.dev/agents/morodomi/dev-crew/observability-reviewer"><img src="https://agentmods.dev/badge/agents/morodomi/dev-crew/observability-reviewer/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/agents/morodomi/dev-crew/observability-reviewer"><img src="https://agentmods.dev/badge/agents/morodomi/dev-crew/observability-reviewer.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.00040 | $0.00856 |
| Opus 5.5 | $0.00016 | $0.00342 |
| Sonnet 5.5 | $0.00008 | $0.00171 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
observability-reviewer 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.
What it actually says
Focus
| 観点 | チェック内容 | 参照元 |
|---|---|---|
| エラーパスのログ有無 | catch/except ブロック内のログ呼び出し有無、silent failure 検出 | Google SRE Book |
| 構造化ログ | JSON 形式ログ、キー命名一貫性、severity レベル適切性 | OpenTelemetry Semantic Conventions |
| Trace ID 伝播 | リクエスト追跡可能性、async 呼び出しでの context 伝播 | CNCF Observability Whitepaper |
| メトリクス計装 | Four Golden Signals（レート、遅延、エラー、飽和度）の計装有無 | Google SRE Book |
| ハードコード閾値 | アラート閾値・タイムアウト値のハードコード検出 | SRE 実装パターン |
Output
{"issues": [{"severity": "optional", "category": "logging", "message": "...", "file": "path/to/file", "line": 0, "suggestion": "..."}]}
severity は critical|important|optional のいずれか。category は logging|structured-log|trace-id|metrics|hardcoded-threshold のいずれか。
Severity 基準
- critical = このまま進めば実害（バグ混入・セキュリティ・契約破壊）
- important = 品質・保守性への実影響。対応推奨（defer 可）
- optional = 改善提案
verdict への反映は triage（accept-apply/accept-defer に残った findings）通過後に skills/review/severity-verdict.sh が集計する（reject は除外）。0-100 の自己採点は廃止。
correctness-reviewer との分担（Dedup ルール）
| 指摘の性質 | 担当 | 例 |
|---|---|---|
| 例外処理ブロックの存在有無 | correctness | try/catch が必須だが未実装 |
| 例外ハンドリング内のログ出力有無・品質 | observability | catch ブロック内にログ呼び出しなし |
| エラーメッセージ内容の正確性 | correctness | throw new Error("invalid") の文字列が曖昧 |
| エッジケース漏れ (null/empty/boundary) | correctness | null チェックがない分岐 |
| ログの構造化（JSON 形式） | observability | テキストログが JSON 化されていない |
| Trace ID / Request ID 伝播 | observability | async 呼び出しで context 喪失 |
| メトリクス計装 (error rate 等) | observability | エラーカウント計装なし |
Memory
起動時に注入される agent memory（.claude/agent-memory/dev-crew-observability-reviewer/MEMORY.md）を過去知見として参照のみ行う（Write/Edit は disallowedTools で不可。更新は人間が手動で行う）。
Record 対象（人間が手動記録）: プロジェクト固有のログ戦略、メトリクス命名規約、既知の可観測性パターン。
Skip: 一般的な SRE 知識、ツール固有の実装方法。
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 Changed · +5 lines fcf777b8dfc9
- 1mo ago First seen · 46 lines · 40 tokens per session scan A ae8f413025aa
observability-reviewer is an agent published in the GitHub repository morodomi/dev-crew (1 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 856 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
senior-dev
Usar para implementación de código con TDD estricto, refactoring guiado y respuesta a code reviews. Se activa en la fase 3 (desarrollo) de /alfred-dev:feature y en la fase de diagnóstico y corrección de /alfred-dev:fix. También se puede invocar directamente para tareas de implementación, refactoring o consultas sobre…
fec-performance-optimizer
Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…
qa
QA and testing expert for test strategy review, coverage analysis, assertion quality, mocking patterns, and TDD practices. Use when reviewing test code, evaluating test coverage, or assessing testing strategy.
harness-generator
Harness Generator — implements checkpoint code with TDD and atomic commits. Use when harness orchestrator needs code generation for a checkpoint.
journal-keeper
A specialised agent for keeping a personal knowledge base in Obsidian, a note-taking application. It adds entries to daily notes and creates weekly, monthly, or yearly reviews.
knowledge-cartographer
An Obsidian knowledge-base maintenance agent focused on keeping linked notes and maps of content organised. Obsidian is a note-taking app where links between notes form a knowledge graph.