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 LambdaTest/agent-skills --skill rook-skillgit clone --depth 1 https://github.com/LambdaTest/agent-skillsWrote 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/lambdatest/agent-skills/rook-skill)<a href="https://agentmods.dev/skills/lambdatest/agent-skills/rook-skill"><img src="https://agentmods.dev/badge/skills/lambdatest/agent-skills/rook-skill/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/lambdatest/agent-skills/rook-skill"><img src="https://agentmods.dev/badge/skills/lambdatest/agent-skills/rook-skill.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.00052 | $0.01265 |
| Opus 5.5 | $0.00021 | $0.00506 |
| Sonnet 5.5 | $0.00010 | $0.00253 |
| Haiku 4.5 | $0.00005 | $0.00127 |
Grade A, and why
rook-skill 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 3d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test agents with Rook
Use Rook to derive scenarios, invoke the target and grade the evidence. Respect requests to use another tool. For saved-result requests, read the supplied files without starting setup, a new run or paid analysis.
Your role
You are the orchestrator: you choose and run Rook commands, and Rook does the
testing work. Discovery is rook explore, test design is rook generate, and
invocation and grading are rook run and rook report. When the user asks to
explore, understand, plan tests for or test an agent, run the matching command.
Do not read the target's code to describe the agent, or write your own test
plan or verdicts, in its place. Answer from Rook's agents, scenarios and
verdicts. Read the target's source only for a step Rook needs from you, such as
a profile's transport and command, or to explain a Rook result. If credits or
authorization block the next command, name it and what it needs; manual
analysis is not a substitute.
Setup and execution
Check rook --version and use rook help <command> for the installed CLI's
options. If Rook is missing, use the
installation instructions.
Use this workflow across compatible releases; a different version alone is not
a reason to stop or change the installation. If a command or output differs,
consult its help and release notes before adapting that step. Keep completion
and evidence checks intact; do not guess missing fields or retry paid work to
probe compatibility. Installation changes still require authorization.
rook doctor
rook status --json
rook plan --json
Use the next command needed by the current state:
| Need | Command |
|---|---|
| Sign in | rook login; in CI, export LT_USERNAME and LT_ACCESS_KEY (no login step) |
| Select a project | rook project use <id> or rook project create <name> |
| Discover agents | rook explore . --json |
| Select an agent | rook agent use <id> |
| Generate scenarios | rook generate --json |
| Create/test a profile | rook profile add <name> --from <file> or --command '<argv>'; then rook profile test --goal "<reply-only goal>" |
| Run | rook sync --yes before rook run --json, or rook run --test --json for a local result |
| Read results | rook report <run-id> --json |
What ships with it
7 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.
- 3d ago First seen · 105 lines · 52 tokens per session scan A 78f6888b1eb6
rook-skill is a skill published in the GitHub repository LambdaTest/agent-skills (376 stars, last pushed 3d ago), licensed MIT. It adds 52 tokens to every session and 1,265 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-10-14.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
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.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
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.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.