Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/MilkyWay008/Hermes-OTGnpx agentmods add skills/milkyway008/hermes-otg/app-debug-workflowWrote 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/skills/milkyway008/hermes-otg/app-debug-workflow)<a href="https://agentmods.dev/skills/milkyway008/hermes-otg/app-debug-workflow"><img src="https://agentmods.dev/badge/skills/milkyway008/hermes-otg/app-debug-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.
<a href="https://agentmods.dev/skills/milkyway008/hermes-otg/app-debug-workflow"><img src="https://agentmods.dev/badge/skills/milkyway008/hermes-otg/app-debug-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 649 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 767 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Rogue Agent · line 468 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00064 | $0.21857 |
| Opus 5.5 | $0.00026 | $0.08743 |
| Sonnet 5.5 | $0.00013 | $0.04371 |
| Haiku 4.5 | $0.00006 | $0.02186 |
Grade A, and why
app-debug-workflow scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
If the server process exits immediately (exit code 1) without printing any server startup banner, the most likely cause is an import-time error in Python (e.g., `import nonexistent_module` deliberately placed in a route How it starts
The opening of the file, as written. The whole thing — 1,317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Debug Workflow
Overview
This workflow is purpose-built for auditing an unfamiliar codebase under time pressure. It inverts the complex-project-workflow — instead of building from scratch, we start from an existing (buggy) codebase and work backward to find and fix issues.
Core loop: Discover → Duck-Verify → Plan → Handoff → Fix → Validate (iterate)
Multi-session architecture (optional — context health fallback):
- Default (single session): Run Phases 0-6 in one session. Simpler, no handoff overhead.
- Fallback (multi-session): If context health degrades (ECHO 🟡/🔴), split into Session A (debug/plan, Phases 0-4+6) and Session B (fix, Phase 5). Handoff docs in
debug-fix-handoff/make this seamless. - Why prepare for multi-session: The fix session (Phase 5) produces heavy tool call volume — reading files, editing, testing, repeating. Keeping this in the main session accelerates context degradation. The handoff exists to protect the primary session's context health.
- Session A (Debug/Plan): Exploration, discovery, rubber-duck audit, task planning, handoff doc creation — NO code writing
- Session B (Fix): Execute fixes from task registry via subagents/ACP — NO planning
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 1,317 lines · 64 tokens per session scan A 9c30fa28c56a
app-debug-workflow is a skill published in the GitHub repository MilkyWay008/Hermes-OTG (20 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 21,857 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
patch-edit
Apply one rewrite-plan step at a time as small reviewable file edits, never rewriting whole files when a localised change suffices.
stage-refactor-checklist
Comprehensive checklist for refactoring a schemacompiler stage folder. Use EVERY TIME you refactor a compiler stage (resolve, unify, codegen, etc.). Read this before writing any code.
invariant-first-coding
Reason from proven invariants before coding. Use when reviewing fallback logic, narrowing types, handling conversions, deciding whether an error path is real or impossible, removing overdefensive code, or when the user questions whether code is being too theatrical, too hedged, or not fail-closed enough.
state-machine-dfa
Document state machines with mermaid diagrams and DFA transition files. Use when writing, reviewing, or adding state-driven logic to modules that have sequential phase transitions, lifecycle management, or protocol handshakes.
daily-bugfix-check
Check the current author's commits from the last 24 hours and proactively find and fix any bugs they introduced. Use when the user asks for a daily bugfix check, wants to review today's commits for issues, or asks to "check my recent code for bugs." Combines commit review with the recent-code-bugfix workflow.
grill-with-docs
Cross-examine codebase architecture against official library documentation and API specs. Identifies deprecations, anti-patterns, and suboptimal library usage.