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 sparko161-droid/pyrus_mcp_bd_complect --skill pyrus-form-scriptsgit clone --depth 1 https://github.com/sparko161-droid/pyrus_mcp_bd_complectWrote 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/sparko161-droid/pyrus_mcp_bd_complect/pyrus-form-scripts)<a href="https://agentmods.dev/skills/sparko161-droid/pyrus_mcp_bd_complect/pyrus-form-scripts"><img src="https://agentmods.dev/badge/skills/sparko161-droid/pyrus_mcp_bd_complect/pyrus-form-scripts.svg" alt="Measured on agentmods" 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.00049 | $0.00945 |
| Opus 5 | $0.00024 | $0.00473 |
| Sonnet 5 | $0.00010 | $0.00189 |
| Haiku 4.5 | $0.00005 | $0.00094 |
Grade A, and why
pyrus-form-scripts 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 7d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Pyrus Client Form Script Developer
This skill provides step-by-step guidance, code structures, API reference, safety constraints, and checklists for building interactive Client Form Scripts in Pyrus.
When to Use This Skill
Use this skill whenever you need to:
- Write or edit JavaScript/TypeScript scripts executed in Pyrus form UI (in browser or mobile app).
- Automate form field calculations (
setValue,setValues). - Add real-time field validation (
validate,validateAsync). - Implement dynamic catalog filtering (
setFilter,setFilterAsync). - Control field visibility (
setVisibility) or assignees (setAssignee). - Calculate working days (
getDaysCount) or aggregate table columns (cost.sum).
1. Key Rules for Client Form Scripts
- Prerequisite Gate: NEVER start writing scripts until ТЗ, Catalogs, JSON Form Upload, and Form Verification via
pyrus:dumpare 100% completed. - Execution Context: Runs in the user's browser/mobile app when filling out a form in real-time.
- Top-level Chains: Subscriptions
form.onChange(...)MUST be declared at the top level of the script. - Field Codes: Field codes must be unique in the form and match standardized codes across forms (
client_name,inn,order_date, etc.). - No Direct HTTP:
fetch(),XMLHttpRequest, and external network calls are FORBIDDEN. Useform.getCatalog(),form.fetchRoles(),form.fetchRegister(). - 5-Second Timeout: Operations must finish within 5 seconds.
- Always set
executeOnLoad = true: Passtrueas 2nd parameter toform.onChange(fields, true)so calculations run when opening existing tasks. - Code Articles in KB: Always run
npm run mirror:scriptsafter writing/updating script code to generate.ts.mdarticles for Pyrus KB sync.
2. API Quick Reference
Methods on form.onChange(fields, executeOnLoad):
.setValue('TargetCode', state => newValue).setValues(['Code1', 'Code2'], state => [val1, val2]).setValueAsync('TargetCode', async state => await newValue).setAssignee(state => personId).validate('FieldCode', state => ({ errorMessage: "Error", canSave: false })).setFilter('CatalogField', state => ({ values: [1, 2, 3] })).setVisibility(['FieldCode'], state => boolean)
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.
- 7d ago First seen · 70 lines · 49 tokens per session scan A 5a95bd4314b3
pyrus-form-scripts is a skill published in the GitHub repository sparko161-droid/pyrus_mcp_bd_complect (0 stars, last pushed 17d ago), licensed Apache-2.0. It adds 49 tokens to every session and 945 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-08-31.
Other skills, from other repositories
fast-typescript-check
Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…
onejs-setup-and-overview
Use this skill whenever the user wants to build or set up user interface in a Unity project using OneJS, React, TypeScript, or JSX, e.g. 'add a main menu to my game', 'build a settings screen', 'make a HUD', 'set up OneJS', 'my OneJS panel is blank', 'the UI is not hot reloading'. Covers confirming OneJS is installed…
coding-standards
A set of general coding standards and practical patterns for TypeScript, JavaScript, React, and Node.js. It covers readable naming, simple designs, avoiding repetition, and delaying unnecessary features.
typescript-rules
React/TypeScript frontend development rules including type safety, component design, state management, and error handling. Use when implementing React components, TypeScript code, or frontend features.
electron-development
Electron development guidelines for building cross-platform desktop applications with JavaScript/TypeScript.
typescript-best-practices
TypeScript best practices. Use when reading or editing any .ts or .tsx file.