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 agentmods add commands/nimbalyst/nimbalyst/playwrightgit clone --depth 1 https://github.com/nimbalyst/nimbalystWhat 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 | $0.00015 | $0.02550 |
| Opus 5 | $0.00008 | $0.01275 |
| Sonnet 5 | $0.00003 | $0.00510 |
| Haiku 4.5 | $0.00002 | $0.00255 |
Grade A, and why
playwright 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 yesterday.
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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright E2E Test Instructions
You are writing Playwright E2E tests for the Nimbalyst editor. Follow these rules STRICTLY.
Critical Rules
1. NEVER Hardcode Selectors
Import and use selectors from PLAYWRIGHT_TEST_SELECTORS in e2e/utils/testHelpers.ts.
// BAD - NEVER DO THIS
await page.locator('.tab-dirty-indicator').toBeVisible();
await page.locator('[contenteditable="true"]').click();
// GOOD - Use shared selectors AND target by document path
import { PLAYWRIGHT_TEST_SELECTORS, getTabByFileName } from '../utils/testHelpers';
const tab = getTabByFileName(page, 'test.md');
await expect(tab.locator(PLAYWRIGHT_TEST_SELECTORS.tabDirtyIndicator)).toBeVisible();
// For editors, scope to the specific file's editor
const editor = page.locator(`[data-filepath="${filePath}"]`);
await editor.locator(PLAYWRIGHT_TEST_SELECTORS.contentEditable).click();
If a selector doesn't exist in PLAYWRIGHT_TEST_SELECTORS, ADD IT THERE first.
2. NEVER Use .first() as a Lazy Escape Hatch
Nimbalyst is a complex app with multiple windows, multiple editor tabs, multiple AI sessions, etc. You MUST target elements precisely.
// BAD - Lazy, will break with multiple tabs/editors
await page.locator('.tab').first().click();
await page.locator('.monaco-editor').first().type('hello');
await page.locator('[contenteditable="true"]').first().click();
// GOOD - Target precisely using data attributes
await page.locator('[data-testid="tab"][data-filepath="/path/to/file.md"]').click();
await page.locator('[data-testid="monaco-editor"][data-filepath="/path/to/file.ts"]').type('hello');
If you can't target an element precisely:
- ADD a
data-testidattribute to the component - ADD a
data-filepath,data-session-id, or other identifying data attribute - Update
PLAYWRIGHT_TEST_SELECTORSwith the new selector - THEN write the test
Common data attributes we use:
data-testid- Unique identifier for test targetingdata-filepath- Full path to file for editors/tabsdata-filename- Filename for simpler casesdata-session-id- AI session identifierdata-tab-type- "document" or "session"data-active- "true"/"false" for active state
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.
- yesterday First seen · 286 lines · 15 tokens per session scan A 4396eed0d272
playwright is a command published in the GitHub repository nimbalyst/nimbalyst (1,609 stars, last pushed 3d ago), licensed MIT. It adds 15 tokens to every session and 2,550 once invoked, about $0.0001 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 commands, from other repositories
agentlas
Agentlas commands — one entry point for network, build, storm, call, and the rest.
agentlas-login
Sign this machine into Agentlas (opens the browser sign-in window).
council-extract
Extract a completed Perplexity Model Council response from the current browser tab, converting it to structured markdown with model attribution, and save to disk.
export-to-council
Query 3 frontier AI models (GPT-5.2, Claude Sonnet 4.5, Gemini 3 Pro) via Perplexity API or browser automation, then synthesize findings. Automatically enters plan mode to study implementation.
labs-perplexity
Run a query using Perplexity's /labs mode via Playwright browser automation. Similar to /research-perplexity but uses Perplexity's experimental labs mode with a longer 15-minute timeout for complex queries.
auto-verify
프론트엔드 UX 검증 — Playwright 기반 비주얼 검증을 실행합니다.