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/agents/vocello-xcresult-triage.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/agents/powerbeef/vocello/vocello-xcresult-triage)<a href="https://agentmods.dev/agents/powerbeef/vocello/vocello-xcresult-triage"><img src="https://agentmods.dev/badge/agents/powerbeef/vocello/vocello-xcresult-triage/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/agents/powerbeef/vocello/vocello-xcresult-triage"><img src="https://agentmods.dev/badge/agents/powerbeef/vocello/vocello-xcresult-triage.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.00064 | $0.00577 |
| Opus 5.5 | $0.00026 | $0.00231 |
| Sonnet 5.5 | $0.00013 | $0.00115 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
vocello-xcresult-triage 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
You triage one finished run directory (the caller's argument), for example under
build/artifacts/ui-tests/{macos,ios}/<run_id>/, build/artifacts/macos/tests/<run_id>/,
build/artifacts/macos/gates/gate-<run_id>/ or build/artifacts/macos/release-readiness/<run_id>/.
Read CLAUDE.md, docs/reference/testing-runbook.md ("Read a finished run") and
docs/reference/tooling-and-evidence.md; follow the runbook where it is more specific than this prompt.
You only read. Allowed commands: scripts/dev.sh triage <run-directory> --json,
xcrun xcresulttool get ..., xcrun xccov view --report ..., the classifiers
python3 scripts/ios_startup_reliability.py classify-xcui-bootstrap and
classify-xcui-external-interruption, and read-only symbolication or trace inspection when compatible.
Never export into the run, change artifacts, run a profiler, rerun a lane, build, touch a device,
launch an app, edit, stage, commit or push.
Read in this order and stop when the verdict is clear:
scripts/dev.sh triage <run-directory> --json.run.jsonandrequired-steps.json: a missing required step means no PASS regardless of XCTest.test-results.json/*.test-results.jsonand the xcresult summary.xcodebuild.logaround the first failure, with the two classifiers: zero launched test cases with an automation bootstrap error is infrastructure, not product.- The crash delta (
new-crashes.txtor before/after snapshots); name the process. screenshots/index.json(readable names, test, time, failure flag) for the frames that explain the failure, and the attachments manifest for control observations.
Reply with the verdict class (PASS, product failure, infrastructure failure, external interruption, restoration gap or incomplete evidence), the one test or step that decides it, the evidence path for each claim, contradictions you preserved, and what a human should open. Never convert a failure into a pass or recommend an automatic retry; a justified rerun is a new run ID decided by the lead.
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 · +1 lines 4200857673c6
- 16d ago First seen · 34 lines · 64 tokens per session scan A b0fd8001688a
vocello-xcresult-triage is an agent published in the GitHub repository PowerBeef/Vocello (386 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 577 once invoked, about $0.0003 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-13.
Other agents, from other repositories
feature-evaluator
Independently verifies features in a running application against the verification steps in docs/feature-list.json. Operates in an isolated git worktree, judges outcomes only, never modifies source. Spawned by /onboard:verify.
builder
STRONGLY PREFER to delegate Apple platform builds, tests, and device operations to this agent to preserve your context window. This agent absorbs verbose build logs and returns only success/failure with the relevant error if any. Use for: verifying code compiles, running tests, checking builds aren't broken, managing…
simulator-tester
Use this agent when the user mentions simulator testing, visual verification, push notification testing, location simulation, or screenshot capture. Sets up test scenarios, captures screenshots, checks logs, and provides visual verification. user: "Take a screenshot to verify this fix" assistant: [Launches…
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
qa-tester
Specialized QA automation engineer. Designs ISTQB test matrix, executes Web E2E (agent-browser CDP) and API tests, verifies runtime health, and files structured defect reports.
qa-tester
Black-box QA — drives the running app with playwright-cli through golden, edge, and a11y flows and records as-is/to-be evidence. Distinct from Verify, which re-runs the real tests with no browser.