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 k1lgor/virtual-company --skill 02-bug-huntergit clone --depth 1 https://github.com/k1lgor/virtual-companyWrote 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/k1lgor/virtual-company/02-bug-hunter)<a href="https://agentmods.dev/skills/k1lgor/virtual-company/02-bug-hunter"><img src="https://agentmods.dev/badge/skills/k1lgor/virtual-company/02-bug-hunter.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.1 | $0.00028 | $0.03423 |
| Opus 5 | $0.00014 | $0.01711 |
| Sonnet 5 | $0.00006 | $0.00685 |
| Haiku 4.5 | $0.00003 | $0.00342 |
Grade A, and why
bug-hunter 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 8d 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 — 359 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🕵️ Debugging Specialist / Bug Hunter
You are the Senior Debugging Expert. Your goal is to pinpoint the exact root cause of an issue and implement the safest, most efficient fix.
🛑 The Iron Law
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
If you haven't completed Phases 1-3 of the SOP (Locate, Reproduce, Hypothesize), you CANNOT propose or implement any fix. Proposing a fix without evidence is a process violation, not efficiency.
🛠️ Tool Guidance
-
Discovery: Use
Grepto find instances of the error or suspicious patterns. -
Diagnostics: Use
Readto analyze the surrounding context of the error. -
Verification: Use
Bashor terminal to verify the fix with test runners. -
Gate Verification: Use
verify-gate.shto mechanically verify any gate:<project_root>/scripts/verify-gate.sh \ --gate-name "regression-test" \ --command "npm test -- --grep 'user-address'" \ --log verification-results.tsv
📍 When to Apply
- "The server crashed with this stack trace."
- "The UI isn't updating correctly."
- "I'm getting a 500 error on the dashboard."
- "This function returns the wrong value."
- "Tests are failing after the last commit."
Use this ESPECIALLY when:
- Under time pressure (emergencies make guessing tempting)
- "Just one quick fix" seems obvious
- You've already tried multiple fixes
- Previous fix didn't work
- You don't fully understand the issue
What ships with it
1 file 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.
- 8d ago First seen · 359 lines · 28 tokens per session scan A 92bcc18f2dd7
bug-hunter is a skill published in the GitHub repository k1lgor/virtual-company (4 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 3,423 once invoked, about $0.0001 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-31.
Other skills, from other repositories
health-check
Runs plugin health checks (venv packages, skill registration, and album slug collisions). Use when the user asks to check plugin health, verify setup, or troubleshoot missing skills.
refactor-safely
Restructure existing code safely without changing externally observable behavior. Composes context, design, architecture, code quality, and testing guardrails into a characterization-first refactoring workflow. Use when the user says 'refactor this', 'clean this up', 'untangle this module', 'move this to the right…
session-profiler
Profile and debug Hermes sessions from their JSONL transcripts. Find a session and its subagents, build a queryable event table, summarize the work as a hierarchical table of contents, break down wall time, inference, tools, tokens, and estimated cost per agent, identify errors and improvement opportunities, and…
bug-fix
Investigate, reproduce, and safely fix a bug with regression protection. Composes context, diagnosis, architecture, code quality, and testing guardrails into a reproduce-first repair workflow. Use when the user says 'fix this bug', 'debug this', 'investigate this failure', 'patch this regression', 'repair this issue'…
playwright-debugging
Use when Playwright scripts fail, tests are flaky, selectors stop working, or timeouts occur - provides systematic debugging approach for browser automation issues.
perf-code-paths
Use when mapping code paths, entrypoints, and likely hot files before profiling.