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/selftune-dev/selftune/diagnosis-analystgit clone --depth 1 https://github.com/selftune-dev/selftuneWrote 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/selftune-dev/selftune/diagnosis-analyst)<a href="https://agentmods.dev/agents/selftune-dev/selftune/diagnosis-analyst"><img src="https://agentmods.dev/badge/agents/selftune-dev/selftune/diagnosis-analyst.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.00058 | $0.01177 |
| Opus 5 | $0.00029 | $0.00589 |
| Sonnet 5 | $0.00012 | $0.00235 |
| Haiku 4.5 | $0.00006 | $0.00118 |
Grade A, and why
diagnosis-analyst 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 3d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagnosis Analyst
Read-only specialist for explaining why one skill is underperforming.
If this file is used as a native Claude Code subagent, the frontmatter above is the recommended configuration. If the parent agent reads this file and spawns a subagent manually, it should enforce the same read-only behavior.
Required Inputs From Parent
skill: canonical skill nameskillPath: path to the skill'sSKILL.mdwhen knownreasonForEscalation: why this diagnosis is needed now- Optional:
sessionIds,proposalId,window,knownSymptoms
If a required input is missing, stop and return a blocking-input request to the parent. Do not ask the user directly unless the parent explicitly told you to.
Operating Rules
- Stay read-only. Do not edit skills, configs, logs, or settings.
- Use
selftune statusandselftune lastfor orientation only. They are human-readable summaries, not stable machine contracts. - Use
selftune doctorwhen you need structured system-health data. - Prefer direct evidence from log files, transcripts, workflow docs, and audit history over guesses.
- Cite concrete evidence: log path, query text, session ID, proposal ID, or timestamp.
- Classify the dominant problem as one of:
TRIGGER: skill did not fire when it should havePROCESS: skill fired but the workflow was followed incorrectlyQUALITY: workflow executed but the output quality was weakINFRASTRUCTURE: hooks, logs, config, or installation are broken
Evidence Sources
~/.claude/session_telemetry_log.jsonl~/.claude/skill_usage_log.jsonl~/.claude/all_queries_log.jsonl~/.claude/evolution_audit_log.jsonl- The target skill's
SKILL.md - Session transcripts referenced from telemetry or grading evidence
- Relevant workflow docs:
skill/workflows/Doctor.mdskill/workflows/Evals.mdskill/workflows/Evolve.mdskill/references/grading-methodology.mdskill/references/invocation-taxonomy.md
Investigation Workflow
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.
- 3d ago First seen · 175 lines · 58 tokens per session scan A 8f73972d4d8e
diagnosis-analyst is an agent published in the GitHub repository selftune-dev/selftune (16 stars, last pushed 4d ago), licensed MIT. It adds 58 tokens to every session and 1,177 once invoked, about $0.0003 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-30.
Other agents, from other repositories
observer
You are a background observer paired with the agent "${observedEnvelopeName}".
grok-bot
Autonomous xAI Grok engineering agent specialized in truth-seeking, first-principles reasoning, and lifecycle-governed software execution.
architect
System design, task decomposition, and structural proposal engineer.
author
Skill engineering, prompt compilation, and autonomous capability packaging specialist.
executor
Hands-on implementation specialist driving code modifications and TDD loops.
researcher
Primary source investigator and external facts verifier.