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/claude-code-skills-1c --skill 1c-web-testgit clone --depth 1 https://github.com/Desko77/claude-code-skills-1cWrote 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/claude-code-skills-1c/1c-web-test)<a href="https://agentmods.dev/skills/desko77/claude-code-skills-1c/1c-web-test"><img src="https://agentmods.dev/badge/skills/desko77/claude-code-skills-1c/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/claude-code-skills-1c/1c-web-test"><img src="https://agentmods.dev/badge/skills/desko77/claude-code-skills-1c/1c-web-test.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.00046 | $0.05756 |
| Opus 5 | $0.00023 | $0.02878 |
| Sonnet 5 | $0.00009 | $0.01151 |
| Haiku 4.5 | $0.00005 | $0.00576 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- 1c-web-test — 94% identical, 193 lines differ
How it starts
The opening of the file, as written. The whole thing — 532 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
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.
- 6d ago First seen · 532 lines · 46 tokens per session scan A e51fa72b9343
1c-web-test is a skill published in the GitHub repository Desko77/claude-code-skills-1c (60 stars, last pushed 7d ago), licensed MIT. It adds 46 tokens to every session and 5,756 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
1c-web-test
A browser-testing tool for the 1C:Enterprise web client. It uses Playwright to navigate screens, fill forms, read tables and reports, and apply filters.
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.
1c-form-validate
A checker for managed forms in 1C, a platform for building business applications. It checks a form's XML structure, identifiers, linked fields, and commands.
1c-meta-validate
A checker for 1C metadata objects stored in XML. It verifies that the object's structure is valid and can optionally compare referenced types with the wider configuration.
1c-xdto-validate
A checker for XDTO packages in 1C:Enterprise. XDTO describes the structure and data types used when 1C exchanges data with external systems.
1c-erf-validate
A checker for the XML source of a 1C external report. It verifies the report structure, properties, fields, tables, forms, layouts, and data-composition schema.