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.
curl -O https://raw.githubusercontent.com/travisennis/acai/master/.agents/skills/manual-testing/SKILL.mdgit 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/manual-testing)<a href="https://agentmods.dev/skills/travisennis/acai/manual-testing"><img src="https://agentmods.dev/badge/skills/travisennis/acai/manual-testing/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/travisennis/acai/manual-testing"><img src="https://agentmods.dev/badge/skills/travisennis/acai/manual-testing.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.00043 | $0.01464 |
| Opus 5.5 | $0.00017 | $0.00586 |
| Sonnet 5.5 | $0.00009 | $0.00293 |
| Haiku 4.5 | $0.00004 | $0.00146 |
Grade A, and why
manual-testing 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.
How it starts
The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manual Testing
Run the acai REPL in a tmux session and interact with it to verify features work correctly. Inspect application logs and session files to confirm internal behavior.
Quick Reference
- Start session:
tmux new-session -d -s acai-test "node source/index.ts" - Send text:
tmux send-keys -t acai-test -l "your prompt" - Submit (Shift+Enter):
tmux send-keys -t acai-test Escape "[13;2u" - Send Shift+Tab:
tmux send-keys -t acai-test Escape "[9;2u" - Send Ctrl+N:
tmux send-keys -t acai-test C-n - Send Ctrl+O:
tmux send-keys -t acai-test C-o - Send Escape:
tmux send-keys -t acai-test Escape - Read screen:
tmux capture-pane -t acai-test -p -S -100 - Kill session:
tmux kill-session -t acai-test
Workflow
1. Start the App
tmux kill-session -t acai-test 2>/dev/null
tmux new-session -d -s acai-test "node source/index.ts"
sleep 2
Wait for the welcome screen to appear before interacting:
tmux capture-pane -t acai-test -p -S -50
Confirm you see the welcome message and the editor prompt.
2. Interact with the REPL
Type text into the editor:
tmux send-keys -t acai-test -l "hello, what mode are you in?"
Submit with Shift+Enter (kitty keyboard protocol):
tmux send-keys -t acai-test Escape "[13;2u"
Wait for the agent to respond, then read the output:
sleep 5
tmux capture-pane -t acai-test -p -S -100
For longer agent runs, poll until the agent finishes (the editor prompt reappears):
for i in $(seq 1 30); do
output=$(tmux capture-pane -t acai-test -p -S -5)
if echo "$output" | grep -q "›"; then
break
fi
sleep 2
done
tmux capture-pane -t acai-test -p -S -100
3. Send Keyboard Shortcuts
Use tmux send-keys for special keys:
| Action | Command |
|---|---|
| Shift+Tab | tmux send-keys -t acai-test Escape "[9;2u" |
| Ctrl+N (new chat) | tmux send-keys -t acai-test C-n |
| Ctrl+O (verbose) | tmux send-keys -t acai-test C-o |
| Escape (interrupt) | tmux send-keys -t acai-test Escape |
| Enter | tmux send-keys -t acai-test Enter |
| Tab | tmux send-keys -t acai-test Tab |
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.
- 2mo ago First seen · 183 lines · 43 tokens per session scan A 60cc70e26d82
manual-testing is a skill published in the GitHub repository travisennis/acai (5 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 1,464 once invoked, about $0.0002 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.
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.…
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…
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.
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.
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.
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.