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 ArabelaTso/Skills-4-SE --skill static-bug-detectorgit clone --depth 1 https://github.com/ArabelaTso/Skills-4-SEWrote 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/arabelatso/skills-4-se/static-bug-detector)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/static-bug-detector"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/static-bug-detector/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/arabelatso/skills-4-se/static-bug-detector"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/static-bug-detector.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00091 | $0.03201 |
| Opus 5 | $0.00046 | $0.01600 |
| Sonnet 5 | $0.00018 | $0.00640 |
| Haiku 4.5 | $0.00009 | $0.00320 |
Grade A, and why
static-bug-detector 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.
How it starts
The opening of the file, as written. The whole thing — 611 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Static Bug Detector
Overview
Perform static analysis on source code to identify potential functional bugs. Detect common bug patterns, analyze control flow and data flow, and report suspicious locations with explanations, severity levels, and confidence assessments.
Bug Detection Workflow
Step 1: Understand the Code
Analyze the code structure and semantics:
-
Identify language:
- Determine programming language
- Understand language-specific semantics
- Note language idioms and conventions
-
Parse code structure:
- Functions/methods
- Classes/types
- Control flow (if, loops, etc.)
- Data flow (assignments, returns)
-
Build context:
- Variable declarations and types
- Function signatures
- Class hierarchies
- Dependencies
-
Identify scope:
- What code to analyze
- Entry points
- Critical paths
Step 2: Detect Bug Patterns
Scan for common bug patterns:
-
Null dereference bugs:
- Variables from nullable sources
- Dereferences without null checks
- Null checks after use
- Undocumented null returns
-
Incorrect conditions:
- Always true/false conditions
- Assignment in condition (= vs ==)
- Redundant conditions
- Inverted logic
- Wrong operators
-
Unreachable code:
- Code after return/throw
- Always-false branches
- Dead code paths
-
Inconsistent state:
- Partial state updates
- Updates without validation
- Non-atomic operations
- Broken invariants
-
Logic errors:
- Off-by-one errors
- Wrong operator precedence
- Infinite loops
- Incorrect boolean logic
-
Resource issues:
- Resource leaks
- Double free/close
- Use after free/close
-
Type issues:
- Type mismatches
- Implicit coercion
- Invalid casts
Step 3: Analyze Severity
Assess the impact of each bug:
High Severity:
- Causes crashes or exceptions
- Data corruption
- Security vulnerabilities
- Guaranteed runtime errors
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.
- 9d ago First seen · 611 lines · 91 tokens per session scan A 7fdc7c5a0acc
static-bug-detector is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (252 stars, last pushed 22d ago), licensed Apache-2.0. It adds 91 tokens to every session and 3,201 once invoked, about $0.0005 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.
Other skills, from other repositories
perf-profiler
A performance investigation guide that uses repeatable measurements and profiling evidence to find where software spends time or resources. Profiling records runtime activity such as CPU use, memory use, database work, or network delays.
log-analyzer
A log-analysis helper that reads application and system logs to find unusual patterns and likely causes. Logs are records of events such as errors, requests, warnings, and service activity.
trace
Trace Elixir call trees from entry points via mix xref. Use when debugging data flow, planning signature changes, or understanding how a bug reaches code.
code-review-web
Review web application code for bugs, security issues, performance problems, and stack-specific anti-patterns. Use this skill whenever the user wants to review code, debug a production issue, investigate a build failure, audit security, or check a PR before merging. Triggers on code review, review my code, debug…
bim-consistency-checker
Check BIM model consistency: naming conventions, parameter completeness, spatial relationships, and data integrity across model elements.
022-root-cause-analysis
Use when a framed problem needs root-cause investigation rather than a symptom-level fix, applying Five Whys, Fishbone (Ishikawa), Current Reality Tree, and constraint identification. This should trigger when an issue's Root Cause Analysis point of view needs evaluation, or when a maintainer directly asks to find the…