application-problem-diagnosis-workflow

application-problem-diagnosis-workflow is a skill for Claude Code, Codex from Dirtytrii/codex-skills. It costs 35 tokens per session (879 once invoked), scanned A, original, no licence file.

A read-only process for diagnosing application incidents by collecting evidence from services, logs, networks, configuration, and user-facing behavior. It proposes a fix only after the evidence is gathered.

In plain words
What is it for?
Use it to investigate application failures, outages, configuration problems, network issues, and broken user workflows.
Why use it?
It reduces guesswork during incidents and helps separate the actual cause from symptoms without changing the running system first.

Skill for Claude CodeCodex

Which agent this was written for is unclear — body not stored (licence); the path alone says nothing.

Good fit Use it to investigate application failures, outages, configuration problems, network issues, and broken user workflows.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dirtytrii/codex-skills/application-problem-diagnosis-workflow
Install

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.

Any agent
npx skills add Dirtytrii/codex-skills --skill application-problem-diagnosis-workflow
Clone the repo
git clone --depth 1 https://github.com/Dirtytrii/codex-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for application-problem-diagnosis-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/dirtytrii/codex-skills/application-problem-diagnosis-workflow/github.svg)](https://agentmods.dev/skills/dirtytrii/codex-skills/application-problem-diagnosis-workflow)
Your own site
<a href="https://agentmods.dev/skills/dirtytrii/codex-skills/application-problem-diagnosis-workflow"><img src="https://agentmods.dev/badge/skills/dirtytrii/codex-skills/application-problem-diagnosis-workflow/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.

agentmods 80×15 button for application-problem-diagnosis-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/dirtytrii/codex-skills/application-problem-diagnosis-workflow"><img src="https://agentmods.dev/badge/skills/dirtytrii/codex-skills/application-problem-diagnosis-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 879 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.00879
Opus 5 $0.00017 $0.00439
Sonnet 5 $0.00007 $0.00176
Haiku 4.5 $0.00003 $0.00088

Measured 9d ago against content hash e04410585dc2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

application-problem-diagnosis-workflow 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 9d 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.

plugins/codex-skills-operations/skills/application-problem-diagnosis-workflow/SKILL.md · 79 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

Changes

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.

  1. 9d ago First seen · 79 lines · 35 tokens per session scan A e04410585dc2

Subscribe to this mod's changes

application-problem-diagnosis-workflow is a skill published in the GitHub repository Dirtytrii/codex-skills (11 stars, last pushed 5d ago), with no licence file. It adds 35 tokens to every session and 879 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

insforge-debug

Use when diagnosing problems in an InsForge project — reactive failures (SDK error object, HTTP 4xx/5xx, gateway timeout 502/503/504, edge function failure or timeout, login/OAuth/auth errors, RLS denial, realtime channel issues, slow query on one endpoint, edge function or Vercel deploy failure), proactive audits…

aiskillstore/marketplace · 107 tokens

binary-re-dynamic-analysis

Use when you need to run a binary, trace execution, or observe runtime behavior. Runtime analysis via QEMU emulation, GDB debugging, and Frida hooking - syscall tracing (strace), breakpoints, memory inspection, function interception. Keywords - "run binary", "execute", "debug", "trace syscalls", "set breakpoint"…

aiskillstore/marketplace · 96 tokens

binary-re-dynamic-analysis

Use when you need to run a binary, trace execution, or observe runtime behavior. Runtime analysis via QEMU emulation, GDB debugging, and Frida hooking - syscall tracing (strace), breakpoints, memory inspection, function interception. Keywords - "run binary", "execute", "debug", "trace syscalls", "set breakpoint"…

aiskillstore/marketplace · 96 tokens

binary-re

This skill should be used when analyzing binaries, executables, or bytecode to understand what they do or how they work. Triggers on "binary", "executable", "ELF", "what does this do", "reverse engineer", "disassemble", "decompile", "pyc file", "python bytecode", "analyze binary", "figure out", "marshal". Routes to…

aiskillstore/marketplace · 103 tokens

binary-re-static-analysis

Use when analyzing binary structure, disassembling code, or decompiling functions. Deep static analysis via radare2 (r2) and Ghidra headless - function enumeration, cross-references (xrefs), decompilation, control flow graphs. Keywords - "disassemble", "decompile", "what does this function do", "find functions"…

aiskillstore/marketplace · 101 tokens

sent-routing-strategist

Decides how a Sent message should reach the recipient — automatic routing versus a pinned channel, what the channel array actually does, how fallback and reroute work, and why a message ended as FAILED, FILTERED, BLOCKED, or channel "auto". Use when choosing the channel field, expecting WhatsApp-to-SMS fallback…

aiskillstore/marketplace · 91 tokens