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 Desko77/cursor-1c-skills --skill 1c-web-testgit clone --depth 1 https://github.com/Desko77/cursor-1c-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/desko77/cursor-1c-skills/1c-web-test)<a href="https://agentmods.dev/skills/desko77/cursor-1c-skills/1c-web-test"><img src="https://agentmods.dev/badge/skills/desko77/cursor-1c-skills/1c-web-test/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/desko77/cursor-1c-skills/1c-web-test"><img src="https://agentmods.dev/badge/skills/desko77/cursor-1c-skills/1c-web-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.05649 |
| Opus 5 | $0.00023 | $0.02825 |
| Sonnet 5 | $0.00009 | $0.01130 |
| Haiku 4.5 | $0.00005 | $0.00565 |
Grade A, and why
1c-web-test 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 6d 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.
This is a copy
94% identical to 1c-web-test — 193 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 — 525 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/web-test - Browser automation for 1C web client
Automates user interactions with 1C:Enterprise web client via Playwright - navigating sections, filling forms, reading tables and reports, filtering lists.
Quick start
RUN="skills/1c-web-test/scripts/run.mjs"
# One-shot: opens browser → runs script → closes browser → exits
node $RUN run http://localhost:8081/bpdemo test-scenario.js
# Or pipe inline:
cat <<'SCRIPT' | node $RUN run http://localhost:8081/bpdemo -
await navigateSection('Продажи');
await openCommand('Заказы клиентов');
await clickElement('Создать');
await fillFields({ 'Клиент': 'Альфа' });
await clickElement('Провести и закрыть');
SCRIPT
Setup (first time)
cd skills/1c-web-test/scripts && npm install
Requires Node.js 18+. npm install downloads Playwright and Chromium.
URL resolution
Read .v8-project.json from project root. Each database has id and optional webUrl.
Construct URL as http://localhost:8081/<id> or use webUrl if set.
Use /web-publish first if the database is not published.
Execution modes
Autonomous mode (preferred for complete scenarios)
node $RUN run <url> script.js # exits when done, no session
Interactive mode (step-by-step development)
# 1. Start session (run_in_background=true, prints JSON when ready)
node $RUN start <url>
# 2. Execute scripts against running session
cat <<'SCRIPT' | node $RUN exec -
const form = await getFormState;
console.log(JSON.stringify(form, null, 2));
SCRIPT
# 2b. Execute without video recording (for debugging/testing)
cat script.js | node $RUN exec - --no-record
# 3. Screenshot
node $RUN shot result.png
# 4. Stop (logout + close)
node $RUN stop
start runs an HTTP server in background. Use exec/shot/stop from other shells.
Writing exec scripts
All browser.mjs exports are globals - no import needed.
console.log output is captured in the JSON response.
writeFileSync / readFileSync also available.
What ships with it
6 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.
- 6d ago First seen · 525 lines · 46 tokens per session scan A 426c0a2fe689
1c-web-test is a skill published in the GitHub repository Desko77/cursor-1c-skills (55 stars, last pushed 7d ago), licensed MIT. It adds 46 tokens to every session and 5,649 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to 1c-web-test, differing in 193 lines, and is treated as a copy.
Other skills, from other repositories
1c-web-test
A browser-automation tool for testing the 1C:Enterprise web client. It uses scripted actions to navigate screens, fill forms, read tables and reports, and apply filters.
1c-vanessa-steps
A searchable catalogue of 1,569 Vanessa Automation steps, with tools for finding steps and checking Gherkin scenarios. Gherkin is the plain-language format used by behavior-driven tests, where each sentence maps to an implemented test action.
web-test
A browser-testing tool for 1C:Enterprise, an enterprise business software platform, using Playwright to automate the web client.
web-test
A browser-automation tool for testing the 1C:Enterprise web client. It uses Playwright to navigate sections, fill forms, read tables and reports, and perform user actions in a browser.
web-test
A skill for checking a 1C system through its web interface in an interactive browser session.
playwright-test
A skill for creating automated browser tests with Playwright, a tool that checks websites by controlling a real browser. The provided information does not describe its other uses.