Borrowing it
Nothing to install: this file belongs to standardbeagle/agnt. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/standardbeagle/agnt/main/.claude/skills/daemon-debug/SKILL.mdgit clone --depth 1 https://github.com/standardbeagle/agntWrote 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/standardbeagle/agnt/daemon-debug)<a href="https://agentmods.dev/skills/standardbeagle/agnt/daemon-debug"><img src="https://agentmods.dev/badge/skills/standardbeagle/agnt/daemon-debug/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/standardbeagle/agnt/daemon-debug"><img src="https://agentmods.dev/badge/skills/standardbeagle/agnt/daemon-debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Data Exfiltration · line 74 Code or instructions that leak agent conversation context to external services, potentially exposing sensitive user interactions.Fix: Remove any code that sends prompts, responses, or session data externally. Preserve user privacy; never exfiltrate conversation content.
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.00024 | $0.01356 |
| Opus 5.5 | $0.00010 | $0.00542 |
| Sonnet 5.5 | $0.00005 | $0.00271 |
| Haiku 4.5 | $0.00002 | $0.00136 |
Grade A, and why
daemon-debug 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.
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daemon Debugging
Use this skill when diagnosing why processes aren't starting, proxies are missing, ports are occupied, or the autostart flow isn't working.
Diagnostic Checklist
Work through these in order. Each step either finds the problem or rules out a category.
1. Verify Daemon State
# Is the daemon running?
agnt daemon status
# What processes does the daemon know about?
printf 'PROC LIST\n;;\n' | socat - UNIX-CONNECT:/tmp/devtool-mcp-$(id -u).sock
# What proxies exist?
printf 'PROXY LIST\n;;\n' | socat - UNIX-CONNECT:/tmp/devtool-mcp-$(id -u).sock
Decode base64 JSON responses. Check:
- Are expected processes listed?
- What state are they in? (running / failed / etc.)
- Do running processes have
urlspopulated? - Are any warnings present (rogue processes)?
2. Check Config
# Read the project config
cat /path/to/project/.agnt.kdl
For each proxy with script set:
- Does the linked script exist in
scripts {}? - Does the script have
url-matchers? Do they match actual output format? - Does the proxy have
fallback-port? (safety net if URL detection fails)
3. Verify URL Detection
URL detection is the #1 failure point for script-linked proxies.
Common URL matcher mismatches:
| Dev server | Actual output | Correct matcher |
|---|---|---|
| dotnet | Now listening on: http://localhost:6111 |
"Now listening on: {url}" |
| Vite | Local: http://localhost:5173/ |
"Local:\\s+{url}" |
| Next.js | - Local: http://localhost:3000 |
"Local:\\s+{url}" |
| Flask | Running on http://127.0.0.1:5000 |
"Running on {url}" |
How to test: Check process output for the URL line, then verify the matcher pattern (with {url} removed) matches as a regex substring.
4. Check Port Bindings
# Linux: what's listening on expected ports?
ss -tlnp | grep -E ':(6111|6112|3000|5173)\b'
# Compare against daemon's tracked processes
# If port is occupied by a PID the daemon doesn't own → rogue process
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 · 138 lines · 24 tokens per session scan A 748b68c5ed0c
daemon-debug is a skill published in the GitHub repository standardbeagle/agnt (22 stars, last pushed today), licensed Apache-2.0. It adds 24 tokens to every session and 1,356 once invoked, about $0.0001 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-30.
Other skills, from other repositories
oh-my-posh
Install, configure, or troubleshoot Oh My Posh/ohmyposh: shell init, themes, segments, Nerd Font icons, and prompt setup on PowerShell, zsh, bash, or fish.
network-rca
Kubernetes network root cause analysis skill powered by Kubeshark MCP. Use this skill whenever the user wants to investigate past incidents, perform retrospective traffic analysis, take or manage traffic snapshots, extract PCAPs, dissect L7 API calls from historical captures, compare traffic patterns over time, detect…
pinchtab-dev
Develop and contribute to the PinchTab project. Use when working on PinchTab source code, adding features, fixing bugs, running tests, or preparing PRs. Triggers on "work on pinchtab", "pinchtab development", "contribute to pinchtab", "fix pinchtab bug", "add pinchtab feature".
code-changes
Workflow for any task that ends in code changes: issue analysis or triage, pull request review comments, features, bug fixes, refactors. Invoke at the start of such a task, before reading or writing code.
printing-press-amend
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally…
printing-press-output-review
Internal sub-skill: agentic review of a printed CLI's sampled command output for plausibility issues that rule-based checks can't encode (substring-match relevance, format bugs, silent source drops, ranking failures). Invoked via the Skill tool by the main printing-press skill at Phase 4.85 and printing-press-polish…