A browser-based evidence collector tied to a work ticket. It navigates an application, takes screenshots or records the flow, and produces proof of how the ticket's behavior works.

Use it to demonstrate a ticket's user flow, attach proof to the ticket, or keep the evidence locally, with an already-running app or a provisioned environment.

It gives a ticket concrete evidence instead of relying only on a description or code review. It is for proving behavior and does not replace the broader pre-pull-request quality checks.

evidence — Command for coding agents by HigorAlves: A browser-based evidence collector tied to a work ticket.

Install

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.

agentmods

npx agentmods add commands/higoralves/orc/evidence

Clone the repo

git clone --depth 1 https://github.com/HigorAlves/orc

Or install orc, the plugin that ships this one along with the rest of its 80 skills, 30 commands, 14 agents, 5 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/higoralves/orc/evidence.svg)](https://agentmods.dev/commands/higoralves/orc/evidence)

Your own site

<a href="https://agentmods.dev/commands/higoralves/orc/evidence"><img src="https://agentmods.dev/badge/commands/higoralves/orc/evidence.svg" alt="Measured on agentmods" height="20"></a>

Per session 47 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,595 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00047	$0.01595
Opus 5	$0.00023	$0.00797
Sonnet 5	$0.00009	$0.00319
Haiku 4.5	$0.00005	$0.00160

Measured 5d ago against content hash dcc1a8716d68, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

evidence scanned grade A with 1 finding 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 5d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Bash(curl:*)

orc/commands/evidence.md · 90 lines

How it starts

The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/orc:evidence

Collect browser evidence that a ticket's behavior works — navigate, screenshot, record — then deliver it to the ticket or keep it local. Unlike /orc:qa (a pre-PR gate scoped to your diff that also runs tests/lint), this is scoped to a ticket (or a flow you describe) and does only the evidence loop. Use it to attach proof to a ticket, demo a flow, or QA a ticket you didn't necessarily write the code for.

Collection reuses /orc:qa's browser drivers verbatim; delivery reuses the orc:evidence-publish skill. This command is only the ticket-first orchestrator — it invents no new browser or upload logic.

Arguments

<TICKET-KEY> — the ticket to scope from and (on upload) deliver to. Omit to use the session's bound jiraTicket, or to run context-only.
--context "<what to test>" — describe the flow to exercise, instead of (or on top of) pulling it from the ticket.
--web <url> — app already running at this URL; skip env provisioning.
--driver chrome|agent-browser — browser driver; default is the same Phase 4.1 gate as /orc:qa. chrome = Claude-in-Chrome, watch live in your browser; agent-browser = headless CLI validator.
--no-env — skip Docker provisioning; use --web or a legacy boot.
Workspace flags (--repos/--repo/--this-repo) — as in /orc:qa.

Workflow

Phase 0 — Context + ticket

!orc-workspace-detect --banner

Context is injected above (ORC_* vars exported; don't re-run detection). Resolve the target ticket: positional <KEY> → session's bound jiraTicket (orc-state get --field jiraTicket, read-for-data per orc:state-protocol) → AskUserQuestion: Provide a key / Run context-only (save locally, no delivery) / Cancel. A key is optional — context-only runs still collect and save the packet, just with no delivery target.

Phase 1 — Scope the run

Build the golden-path scope from, in precedence order: --context, the ticket body, both. When a key resolved and acli jira auth status exits 0:

Read the full file on GitHub · 90 lines

Changes

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.

5d ago First seen · 90 lines · 47 tokens per session scan A dcc1a8716d68

Subscribe to this mod's changes

evidence is a command published in the GitHub repository HigorAlves/orc (6 stars, last pushed 8d ago), licensed MIT. It adds 47 tokens to every session and 1,595 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Browser automation claude plugin

evidence

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Makes network callslowCapability

How it starts

/orc:evidence

Arguments

Workflow

Phase 0 — Context + ticket

Phase 1 — Scope the run

What this file has done since we first saw it

Other commands, from other repositories

use-isolated-browser

sync

auto-browse

ccboard-web

webapp-testing

t800-onboard