Borrowing it
Nothing to install: this file belongs to PowerBeef/Vocello. 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/PowerBeef/Vocello/main/.claude/skills/vocello-debug/SKILL.mdgit clone --depth 1 https://github.com/PowerBeef/VocelloWrote 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/powerbeef/vocello/vocello-debug)<a href="https://agentmods.dev/skills/powerbeef/vocello/vocello-debug"><img src="https://agentmods.dev/badge/skills/powerbeef/vocello/vocello-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/powerbeef/vocello/vocello-debug"><img src="https://agentmods.dev/badge/skills/powerbeef/vocello/vocello-debug.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.00028 | $0.00366 |
| Opus 5.5 | $0.00011 | $0.00146 |
| Sonnet 5.5 | $0.00006 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
vocello-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 2d 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.
What it actually says
Evidence-first debugging
Arguments: $ARGUMENTS
Read docs/reference/testing-runbook.md and the relevant docs/reference/native-engineering.md or
tooling-and-evidence.md sections. Begin with scripts/dev.sh triage <run-directory> --json when
artifacts exist. Inspect the deciding ledger/test, first raw-log failure, crash delta and attachments.
Classify product failure, infrastructure failure, interruption or incomplete evidence before action.
Load applicable Axiom build/concurrency/performance guidance, swift-mlx/swift-mlx-lm skills for runtime
issues and Sosumi/Context7 for authoritative API research. Hand a finished native run to the read-only
vocello-xcresult-triage agent when a second reading helps. Detect optional MobileBuildMCP/LLDB
capabilities in this session; do not assume a device/LLDB route exists. Keep native serialization;
XCUITest is the only automated UI evidence, and computer use may reproduce a report between lanes
(/vocello-ui-autonomy).
Use verified Axiom xcsym for symbolication and xcprof for existing traces as appropriate; locate
helpers under the Claude plugin cache (scripts/dev.sh doctor --json lists them), check executability
and non-mutating help before use. Never xcui or simulator agents.
Repository raw logs, exit statuses, optimization settings and artifact contracts remain authoritative;
retain script-only fallbacks. Reproduce with the smallest deterministic test or justified new lane ID.
Preserve the original failure. No blanket cache clearing, automatic retry or unsupported PASS claim.
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.
- 2d ago Changed · +2 lines 9664b90ca7b2
- 16d ago Changed · +5 lines 625f9251b9ad
- 18d ago First seen · 20 lines · 28 tokens per session scan A 6fb4d6c3ca78
vocello-debug is a skill published in the GitHub repository PowerBeef/Vocello (386 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 366 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-10-11.
Other skills, from other repositories
localvoxtral-doctor
Use when the user's localvoxtral dictation misbehaves, for example a dictation did not join this session, its text was not inserted, or speech or polish failed. Names the localvoxtral commands that check the setup and read the app's log.
reproduce-bug
Reproduce a reported bug in googleapis/mcp-toolbox and decide whether it is real, delivering an evidence-backed verdict: confirmed, already fixed, misconfiguration, client-side, works as intended, not reproducible, or blocked. Use whenever a maintainer asks you to reproduce, verify, confirm, or investigate a bug…
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
walkthrough
Generate a hands-on browser walkthrough of a PR's user-facing changes to exercise before review; --publish posts the final version to the PR for QA.
quality-engineering-test-healing
Failure taxonomy and allowed/forbidden repairs for a failing E2E test. Use when a Playwright/Maestro/Detox/XCUITest/Espresso/Appium test fails and you must decide whether to repair the test or route to a real bug.