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/mcp-server-guide --skill kanecli-skillgit clone --depth 1 https://github.com/LambdaTest/mcp-server-guideWrote 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/mcp-server-guide/kanecli-skill)<a href="https://agentmods.dev/skills/lambdatest/mcp-server-guide/kanecli-skill"><img src="https://agentmods.dev/badge/skills/lambdatest/mcp-server-guide/kanecli-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/mcp-server-guide/kanecli-skill"><img src="https://agentmods.dev/badge/skills/lambdatest/mcp-server-guide/kanecli-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.00229 | $0.08463 |
| Opus 5.5 | $0.00092 | $0.03385 |
| Sonnet 5.5 | $0.00046 | $0.01693 |
| Haiku 4.5 | $0.00023 | $0.00846 |
Grade A, and why
kanecli-skill 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| 🔌 **API call** | "call", "POST/GET a URL", a pasted `curl` | The agent makes the HTTP request itself; "save the response as X", then assert on it in plain English: "assert the response status is 200", "store the id fr This is a copy
100% identical to kanecli-skill — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kane CLI — Browser Automation Skill
Use kane-cli for any task that requires a real browser: navigating websites, clicking elements, filling forms, searching, testing web UI, taking screenshots, or verifying deployments. Do NOT use Playwright, Puppeteer, or Selenium directly. Use --agent for run, testmd run, and generate. testrun run has no --agent: it emits NDJSON when stdin is not a TTY (use < /dev/null for terminal automation). Assurance conversational commands use --mode agent.
Authoring test cases or scenarios? Never write them by hand — kane-cli has two authoring pipelines, and the routing matters:
- The user describes what to test in a sentence or two, or wants quick scenario/case ideas →
kane-cli generate(§6). - The user has requirement documents (a PRD, a spec, acceptance notes) and wants a designed suite, requirement-linked coverage, or "what exactly is covered?" answers → the assurance commands — Read
references/assurance.mdfirst.
Don't draft test cases in chat or scratch files: both pipelines produce structured, refinable, runnable _test.md output.
1. Every session: ready check, launch, result card. READ THIS FIRST
A one-line "Test passed" instead of the result card is a bug. A run that starts with no ready check is a bug too. This section is first so you don't miss it. Follow it exactly.
The order never changes: ready check → launch line → the run → result card. On a person's first session two things are added: a short tour sent with the launch line, and three choices asked after the first result. Nothing is asked before the first result.
1.1 Start with the ready check
Before the first kane-cli command of a session, run the preflight script that ships with this skill and show the ready card. It is one short command and takes about two seconds:
sh "<skill dir>/scripts/preflight.sh"
<skill dir> is the folder that holds this SKILL.md. Read references/ready-check.md for the card (a full table on the first session, one line afterwards), the problems that stop a run, and the sign-in flow. Two rules matter enough to repeat here: you start sign-in yourself with kane-cli login --oauth, and you never ask for an access key or password in chat.
What ships with it
24 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.
- references/agent-config.md 5.0 KB
- references/assurance-parsing.md 14 KB
- references/assurance.md 33 KB
- references/cards.md 7.8 KB
- references/context-sync.md 22 KB
- references/debug.md 6.3 KB
- references/evidence.md 4.9 KB
- references/execution-controls.md 1.4 KB
- references/fair-evaluation.md 4.5 KB
- references/first-run.md 9.7 KB
- references/generate-parsing.md 5.0 KB
- references/generate.md 8.2 KB
- references/live-strip.md 5.5 KB
- references/mobile.md 14 KB
- references/objectives-cookbook.md 26 KB
- references/parallel.md 2.9 KB
- references/parsing.md 10 KB
- references/ready-check.md 7.2 KB
- references/setup-and-config.md 10 KB
- references/test-manager.md 8.9 KB
- references/testmd.md 16 KB
- references/testrun.md 18 KB
- scripts/preflight.ps1 8.0 KB runs code
- scripts/preflight.sh 6.5 KB runs code
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 Changed · +229 tokens per session a5131fbbedb7
- 7d ago First seen · 397 lines · 0 tokens per session scan A 8a557f2df100
kanecli-skill is a skill published in the GitHub repository LambdaTest/mcp-server-guide (0 stars, last pushed 4d ago), licensed MIT. It adds 229 tokens to every session and 8,463 once invoked, about $0.0009 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to kanecli-skill, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
browser-qa
Automated visual testing and browser interaction verification.
e2e-testing
Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
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.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.