acai: Skill for Claude Code

.claude/skills/verify/SKILL.md

verify is a skill for Claude Code from travisennis/acai. It costs 20 tokens per session (365 once invoked), scanned A, original, MIT.

A guide for building and testing Acai through its real command-line interface, including its model, tools, and prompts. It explains how to run one-shot checks and avoid misleading test setups.

In plain words
What is it for?
Use it to build Acai, launch its CLI, test tool behavior through a real agent session, and check for leftover processes or other runtime issues.
Why use it?
It helps verify behavior at the same surface users actually run and highlights that these checks can make billed model calls.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is travisennis/acai's own configuration. It tells Claude Code how to work on acai itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything acai configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is ./bin/acai -p "..." # one-shot CLI mode (no alternate screen, easy to capture).

Reuse

Borrowing it

Nothing to install: this file belongs to travisennis/acai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/travisennis/acai/master/.claude/skills/verify/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/travisennis/acai

Made for: Claude Code.

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.

agentmods badge for verify

README.md
[![agentmods](https://agentmods.dev/badge/skills/travisennis/acai/verify/github.svg)](https://agentmods.dev/skills/travisennis/acai/verify)
Your own site
<a href="https://agentmods.dev/skills/travisennis/acai/verify"><img src="https://agentmods.dev/badge/skills/travisennis/acai/verify/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.

agentmods 80×15 button for verify

Your own site · 80×15
<a href="https://agentmods.dev/skills/travisennis/acai/verify"><img src="https://agentmods.dev/badge/skills/travisennis/acai/verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 365 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.00365
Opus 5.5 $0.00008 $0.00146
Sonnet 5.5 $0.00004 $0.00073
Haiku 4.5 $0.00002 $0.00036

Measured 2mo ago against content hash b70004c3e5fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.claude/skills/verify/SKILL.md · 39 lines

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 -p invocations. 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 through tail or strip them when capturing.
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.

  1. 2mo ago First seen · 39 lines · 20 tokens per session scan A b70004c3e5fe

Subscribe to this mod's changes

verify is a skill published in the GitHub repository travisennis/acai (5 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 365 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-08-31.

Related

Other skills, from other repositories

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

omnigent-ai/omnigent · 100 tokens

test-master

Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…

Jeffallan/claude-skills · 104 tokens

eval-dataset-design

A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.

bojieli/ai-agent-book · 138 tokens

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.

callstack/agent-device · 55 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

test-warp-ui

Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.

warpdotdev/warp · 55 tokens