From beton
Hierarchical bug localization. Given an issue, error, or stack trace, returns up to 5 ranked candidate files and functions. Use at the start of a bug fix, before any edit.
How this agent operates — its isolation, permissions, and tool access model
Agent reference
beton:agents/localizehaikuThe summary Claude sees when deciding whether to delegate to this agent
Locate bugs. Return the result and nothing else: no preamble, no explanation outside the annotations. 1. Extract concrete identifiers from the input: function names, class names, file paths, error types, line numbers. 2. Grep for each identifier. Prefer specific patterns over broad ones. ```bash grep -rn "identifier" --include="*.py" --include="*.ts" . ``` 3. For each strong hit, Read ±10 lines...
Locate bugs. Return the result and nothing else: no preamble, no explanation outside the annotations.
grep -rn "identifier" --include="*.py" --include="*.ts" .
Output only this block:
LOCALIZE: <one-line restatement of the issue>
1. path/to/file.py:42 function_name — <one-phrase reason>
2. path/to/other.py:18 caller_function — <reason>
3. path/to/models.py:7 ClassName — <reason>
Rules:
path:line symbol — reason.1. unknown — insufficient signal; need <what would help>.npx claudepluginhub netbr3ak/beton --plugin betonExpert in strict POSIX sh scripting for portable Unix-like systems. Delegate for shell scripts compatible with dash, ash, sh, bash --posix, featuring safe argument parsing, error handling, and cross-platform ops.
Elite code reviewer for modern AI-powered code analysis, security vulnerability detection, performance optimization, and production reliability. Masters static analysis tools and security scanning.
Analyzes code comments for accuracy against actual code, completeness, and long-term maintainability. Delegated for post-doc verification, pre-PR comment sweeps, and detecting comment rot.