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 agentmods add skills/travisennis/acai/verifynpx skills add travisennis/acai --skill verifygit clone --depth 1 https://github.com/travisennis/acaiWrote 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/travisennis/acai/verify)<a href="https://agentmods.dev/skills/travisennis/acai/verify"><img src="https://agentmods.dev/badge/skills/travisennis/acai/verify.svg" alt="Measured on agentmods" 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 | $0.00020 | $0.00365 |
| Opus 5 | $0.00010 | $0.00182 |
| Sonnet 5 | $0.00004 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
verify 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 4d 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
Verifying acai changes
Build and launch
npm run build # compiles to dist/; bin/acai runs dist/index.js
./bin/acai -p "..." # one-shot CLI mode (no alternate screen, easy to capture)
CLI mode (-p) drives the full real agent loop — model, tool registry,
prompts — and prints the final answer plus a session summary to stdout.
It uses the user's real model config (~/.acai/acai.json) and API keys
from the environment, so each run makes billed model calls; keep prompts
small and end them with "Do not run any other commands."
Driving tool behavior
To verify tool-level behavior, tell the model exactly which tool to call and with which parameters, then ask it to report the tool result verbatim (e.g. "report the exact metadata footer line in square brackets"). This reliably exercises Bash/BashSession/etc. through the real agent.
Gotchas
timeout(1)does not exist on this macOS host; bound long runs with the Bash tool's own timeout instead.- Process sessions (Bash yield/BashSession) are in-memory per acai process;
they cannot be verified across separate
-pinvocations. Verify the whole flow inside a single prompt. - Orphan checks: after acai exits,
pgrep -lf <command>confirms session cleanup killed the process group. - stdout includes terminal title escape sequences (
]0;...); pipe throughtailor strip them when capturing.
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.
- 4d ago First seen · 39 lines · 20 tokens per session scan A b70004c3e5fe
verify is a skill published in the GitHub repository travisennis/acai (5 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 365 once invoked, about $0.0001 per session on Opus 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-08-31.
Other skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
solopi-ai
通过 SoloPi 的机器可读 CLI 编译和执行 AI 验证计划，管理签名端侧 ExecuTorch 决策模型、持久设备池、无人值守任务、安卓设备、应用、动作、配置、用例步骤与交互录制、回放及性能历史、动态 Agent、批量与重复执行、性能监控、压力测试和证据。适用于需求/AC 到 Result Judge 三态结论、cloud/on-device 决策切换、模型发布门禁，以及 generation 租约的多设备 CI 执行。.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
local-frontend-check
Smoke-test or verify UI behaviour on the local Jarvis Registry frontend running at http://localhost/gateway. Use for manual regression checks, bug-fix verification, and end-to-end confirmation of specific flows without running the automated test suite.
pr-integration-test
Design, implement, and validate Intelligent Terminal integration tests for a target pull request or regression. Use when asked to add PR integration tests, convert a bug fix into E2E coverage, prove existing behavior still works, map tests to the release checklist, or verify E2E reports mark checklist cases complete.