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 agents/kivo360/omoios/diagnostic_system_gap_analysisgit clone --depth 1 https://github.com/kivo360/OmoiOSWrote 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/kivo360/omoios/diagnostic_system_gap_analysis)<a href="https://agentmods.dev/agents/kivo360/omoios/diagnostic_system_gap_analysis"><img src="https://agentmods.dev/badge/agents/kivo360/omoios/diagnostic_system_gap_analysis.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.00000 | $0.01924 |
| Opus 5 | $0.00000 | $0.00962 |
| Sonnet 5 | $0.00000 | $0.00385 |
| Haiku 4.5 | $0.00000 | $0.00192 |
Grade A, and why
diagnostic_system_gap_analysis 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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Direct Answer: Diagnostic System Status
Created: 2025-11-20 Status: Draft Purpose: Provide a status overview and gap analysis for the diagnostic system, highlighting missing critical components and next steps. Related: docs/diagnostic_system_gap_analysis.md, docs/critical_missing_features.md, docs/design/agents/diagnostic_system.md, docs/implementation/phase5_handoff.md, docs/requirements/agents/diagnostic_system.md
Your Questions:
- How far off is our diagnostic system from the original design?
- Are we missing anything extremely important?
Question 1: How Far Off?
Short Answer: 100% gap — Not implemented yet
Detailed Answer:
Diagnostic System Completion: 0%
We have:
- ❌ No
DiagnosticRunmodel - ❌ No
DiagnosticService - ❌ No stuck workflow detection
- ❌ No evidence collection
- ❌ No hypothesis generation
- ❌ No automatic diagnostic task creation
- ❌ No diagnostic monitoring loop
BUT — This is EXPECTED because:
-
Diagnostic was never in Phase 5 scope
- Phase 5 = Guardian + Memory + Cost + Quality
- Diagnostic is a Phase 6 feature based on design docs
-
We have all the prerequisites:
- ✅ Guardian (emergency intervention)
- ✅ Memory (pattern learning)
- ✅ Task Queue (with dependencies)
- ✅ Event Bus (pub/sub)
- ✅ Agent Registry
-
Foundation is solid:
- 171 tests passing (Phase 3)
- 29 tests passing (Phase 5 Guardian)
- 29 tests passing (Phase 5 Memory)
- Zero linting errors
- Proper schema conventions
Question 2: Are We Missing Anything EXTREMELY Important?
Short Answer: YES — Three things
1. 🚨 Diagnostic Agent System (MOST CRITICAL)
Why extremely important:
Without it, your system can:
- ❌ Get stuck forever after all tasks complete
- ❌ Never recover from "forgot to submit result"
- ❌ Have no idea why workflows stalled
- ❌ Require constant human babysitting
With it, your system can:
- ✅ Detect stuck workflows automatically
- ✅ Analyze what went wrong
- ✅ Create recovery tasks
- ✅ Resume execution without human intervention
- ✅ Learn from failures via Memory integration
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 · 281 lines · 0 tokens per session scan A cf77793fe75a
diagnostic_system_gap_analysis is an agent published in the GitHub repository kivo360/OmoiOS (75 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,924 tokens. 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-30.
Other agents, from other repositories
assistant
You are a general-purpose assistant — the example agent that ships with Archie so a fresh install does something useful out of the box. You handle small, self-contained requests: summarizing a block of text, drafting a short reply, or explaining something plainly.
gatekeeper
You exist to exercise the MCP tool approval gate in end-to-end checks. When asked to call your tools, call them exactly as instructed and report exactly what they returned — no improvisation, no retries beyond what the instructions say.
pm
This is the example PM overlay. The text here is appended to the PM agent's system prompt, so use it to give the PM the standing context it needs for your organization — what the company/team does, who the regular requesters are, house style for replies, and any defaults that should hold across every conversation.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
annotator
Phase 2.5 전용 @AX 태그 스캔 및 적용 에이전트. executor가 수정한 파일 목록을 받아 @AX 태그를 자동으로 분석하고 적용한다.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…