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 nemojs-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/nemojs-skill)<a href="https://agentmods.dev/skills/lambdatest/agent-skills/nemojs-skill"><img src="https://agentmods.dev/badge/skills/lambdatest/agent-skills/nemojs-skill.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 129 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00066 | $0.00905 |
| Opus 5 | $0.00033 | $0.00452 |
| Sonnet 5 | $0.00013 | $0.00181 |
| Haiku 4.5 | $0.00007 | $0.00090 |
Grade A, and why
nemojs-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 8d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nemo.js Automation Skill
PayPal's Selenium-based test automation framework for Node.js.
For TestMu AI cloud execution, see reference/cloud-integration.md and shared/testmu-cloud-reference.md.
Core Patterns
Basic Test (Mocha)
const Nemo = require('nemo');
const { expect } = require('chai');
describe('Login Flow', function() {
this.timeout(30000);
let nemo;
before(async () => {
nemo = await Nemo();
});
after(async () => {
await nemo.driver.quit();
});
it('should login with valid credentials', async () => {
await nemo.driver.get(nemo.data.baseUrl + '/login');
const email = await nemo.view._find('#email');
await email.sendKeys('[email protected]');
const password = await nemo.view._find('#password');
await password.sendKeys('password123');
await nemo.view._find('button[type="submit"]').click();
await nemo.view._waitVisible('.dashboard', 10000);
const url = await nemo.driver.getCurrentUrl();
expect(url).to.include('/dashboard');
});
it('should show error for invalid credentials', async () => {
await nemo.driver.get(nemo.data.baseUrl + '/login');
await nemo.view._find('#email').sendKeys('[email protected]');
await nemo.view._find('#password').sendKeys('wrong');
await nemo.view._find('button[type="submit"]').click();
await nemo.view._waitVisible('.error', 5000);
const error = await nemo.view._find('.error');
const text = await error.getText();
expect(text).to.include('Invalid');
});
});
View Locators
await nemo.view._find('#css-id'); // CSS
await nemo.view._find('.class-name'); // CSS class
await nemo.view._find('[data-testid="login"]'); // Data attribute
await nemo.view._find('xpath://button[@type]'); // XPath prefix
await nemo.view._waitVisible(locator, timeout); // Wait + find
await nemo.view._finds('.items'); // Find multiple
What ships with it
3 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.
- 8d ago First seen · 135 lines · 66 tokens per session scan A 01b75bb01142
nemojs-skill is a skill published in the GitHub repository LambdaTest/agent-skills (367 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 905 once invoked, about $0.0003 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-30.
Other skills, from other repositories
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
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.
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".
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
smoke-test
Run smoke tests against a deployed or local app based on your git diff. Each test uses Skyvern browser tools (navigate, act, validate, screenshot) with Chrome DevTools MCP as fallback. Posts screenshot evidence as PR comments.