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 skills add antropos17/Aegis --skill aegis-diagnosing-bugsgit clone --depth 1 https://github.com/antropos17/AegisWrote 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/antropos17/aegis/aegis-diagnosing-bugs)<a href="https://agentmods.dev/skills/antropos17/aegis/aegis-diagnosing-bugs"><img src="https://agentmods.dev/badge/skills/antropos17/aegis/aegis-diagnosing-bugs/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/antropos17/aegis/aegis-diagnosing-bugs"><img src="https://agentmods.dev/badge/skills/antropos17/aegis/aegis-diagnosing-bugs.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00048 | $0.01020 |
| Opus 5.5 | $0.00019 | $0.00408 |
| Sonnet 5.5 | $0.00010 | $0.00204 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
aegis-diagnosing-bugs 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 today.
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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AEGIS bug diagnosis
Adapted from Matt Pocock's diagnosing-bugs skill; attribution and terms: LICENSE.
Locate the running path
Read the active checkout's AGENTS.md, package.json, relevant memory-bank/progress.md entries and affected source. Use aegis-context for source navigation when available; a worktree without that local skill can use the same root documents directly. Record HEAD, git status and the actual renderer entrypoint from Vite configuration. The skill's installation folder does not select the checkout or running app.
Read relevant memory-bank/ai-mistakes.md entries for identity, audit-chain or Windows worktree changes. Check historical notes against current code rather than reopening work already completed.
Explicit user instructions and existing project authorization govern the task. Continue ordinary authorized diagnosis and fixes without a new plan gate. Do not spawn agents or external AI CLIs unless the user requests delegation. Preserve concurrent work and project restrictions on protected configuration, release actions and lockfiles.
Reproduce before committing to a cause
Describe the exact observed failure and expected behavior. Build a short pass/fail loop through the real failing path: a focused Vitest test, integration harness, Electron/renderer scenario, sidecar self-test or captured-event replay. Read nearby tests and current vitest.config.js. The existing testing explains harness details; consult it when available.
For CommonJS main modules, vi.mock does not intercept native require calls. Reuse init(deps), _setDepsForTest() and _resetForTest() as supported by the subject. Match the nearby createRequire/cache pattern and restore state. Prove the production caller consumed the controlled dependency; a detached module instance can make a convincing but irrelevant test.
Run the reproduction and capture the actual failure. For an intermittent symptom use bounded runs and record incidence. For a performance regression compare the same workload, executable/configuration, observation window and environment. Pin time or input order when appropriate without masking the race being investigated.
What ships with it
2 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.
- today First seen · 48 lines · 48 tokens per session scan A 95b5d82dca7d
aegis-diagnosing-bugs is a skill published in the GitHub repository antropos17/Aegis (157 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 1,020 once invoked, about $0.0002 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-10-17.
Other skills, from other repositories
troubleshoot
Investigate unexpected chat agent behavior by analyzing direct debug logs in JSONL files. Use when users ask why something happened, why a request was slow, why tools or subagents were used or skipped, or why instructions/skills/agents did not load.
agenttrace-session-audit
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
phoenix-observability
Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
repair-github-ci
Fix failing GitHub CI / Actions checks via fixgithubprci and push to the existing PR head, or fix a branch's failing CI via a linked repair worktree.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.