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 HigorAlves/orc --skill evidence-publishgit clone --depth 1 https://github.com/HigorAlves/orcWrote 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/higoralves/orc/evidence-publish)<a href="https://agentmods.dev/skills/higoralves/orc/evidence-publish"><img src="https://agentmods.dev/badge/skills/higoralves/orc/evidence-publish/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/higoralves/orc/evidence-publish"><img src="https://agentmods.dev/badge/skills/higoralves/orc/evidence-publish.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.00049 | $0.01573 |
| Opus 5.5 | $0.00020 | $0.00629 |
| Sonnet 5.5 | $0.00010 | $0.00315 |
| Haiku 4.5 | $0.00005 | $0.00157 |
Grade A, and why
evidence-publish 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 6d 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.
- **attach** available iff comment is available **and** `command -v curl` **and** a token env is set (`JIRA_API_TOKEN` or `ATLASSIAN_API_TOKEN`). Site + email are read from `acli jira auth status`; acli deliberately neve How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evidence Publishing
Take the evidence packet browser QA already wrote to .orc/<branch>/files/qa/ and deliver it: attach the visual proof and post a summary to the linked ticket, or keep it local — always the user's explicit choice, and always safe to run (no tracker ⇒ local-only, no prompt, no error).
Announce at start: "I'm using the evidence-publish skill to deliver the QA evidence."
Collection is NOT this skill's job — /orc:qa (Driver A agent-browser / Driver B Claude-in-Chrome) already produced the packet. This skill owns delivery only: detect → curate → preview-gate → deliver → record.
Inputs
qaDir— the packet directory (.orc/<branch>/files/qa/or.orc/evidence/<KEY>/).ticketKey(optional) — an explicit key; else resolved from the active session.verdict—pass|fail|partialfrom the QA run (used in the comment).
Protocol
1. Detect — tracker enablement ladder
Two capability tiers, checked and degraded independently:
- comment available iff
command -v acliandacli jira auth statusexits 0. - attach available iff comment is available and
command -v curland a token env is set (JIRA_API_TOKENorATLASSIAN_API_TOKEN). Site + email are read fromacli jira auth status; acli deliberately never exposes its stored token, so REST upload needs the user's own.
Resolve the ticket: explicit ticketKey, else the active session's jiraTicket in .orc/orc.json (sanitized-branch match, status == in_progress) — the same resolution /orc:jira bind uses. No ticket, or comment unavailable ⇒ no tracker target (the gate still runs when the Artifact target below is available; otherwise skip to step 5).
Report + Artifact target (independent of the tracker): for a session packet, always render the report — orc-report html writes qaDir/report.html (criteria, notes, screenshots, recording; missing files flagged) and prints its path. The Artifact target is available iff the host exposes the Artifact tool.
What ships with it
5 files 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.
- 6d ago Changed · -7 lines 29357796fc0b
- 19d ago Changed · +7 lines 92163bf6e5e9
- 21d ago Changed · +7 lines 622a7973dffc
- 1mo ago First seen · 85 lines · 49 tokens per session scan A f52e3c5088e2
evidence-publish is a skill published in the GitHub repository HigorAlves/orc (7 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 1,573 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
proof-e2e
Build E2E test specs for critical user journeys — Playwright or Cypress, page objects, setup/teardown, CI config. Use when asked to "write E2E tests", "end-to-end testing", "browser tests", "UI tests", or "Playwright tests".
proof-strategy
Produce a test strategy for a project or feature — risk map, test type decisions, coverage targets, CI config. Use when asked to "create test strategy", "what should we test", "testing plan", or "improve test coverage".
e2e
Orchestrates e2e testing: BDD scenarios, Playwright autotests. Triggers: e2e tests, BDD scenarios, write autotest.
e2e-panther-playwright
Write end-to-end tests with Symfony Panther 2.4 for browser automation or Playwright for complex scenarios.
functional-tests
Write functional tests for Symfony controllers and HTTP endpoints using WebTestCase, getContainer, loginUser, and DAMA rollback.
proof-recon
Testing reconnaissance — inventory all tests, frameworks, coverage, CI integration, and assess testing maturity for project takeover. Use when asked to "understand the tests", "testing assessment", "what's tested", or "test inventory".