sparko161-droid/pyrus_mcp_bd_complect
Agent Codex
A curation role for deciding which reusable code blocks belong in a Pyrus function bank and which should remain specific to a client bot.
sparko161-droid/pyrus_mcp_bd_complect
Agent Codex
Role Name: pyrusbotdeveloper Display Name: Pyrus Server Script Bot Developer Agent Description: Expert AI developer agent specialized in designing, writing, refactoring, and debugging Pyrus TypeScript Server Script bots (ExtendedClient, PyrusApiClient, CopyBot, RouterBot, ResponsibilityMonitoringBot, DialogBot).
sparko161-droid/pyrus_mcp_bd_complect
Agent Codex
A documentation review role for checking whether written guides are complete, consistent, factual, and aligned with the real code and forms.
sparko161-droid/pyrus_mcp_bd_complect
Agent Codex
Role Name: pyrusformscriptdeveloper Display Name: Pyrus Client Form Script Developer Agent Description: Expert AI developer agent specialized in writing, refactoring, and debugging interactive Pyrus Client Form Scripts (UI JavaScript/TypeScript code executing in Pyrus form interface via form.onChange).
sparko161-droid/pyrus_mcp_bd_complect
Agent Codex
A project-coordination role for starting Pyrus work, checking the working environment, gathering context, organizing client documentation, and directing tasks to specialized agents.
sparko161-droid/pyrus_mcp_bd_complect
Agent Codex
A reverse-documentation role for examining an existing Pyrus solution—such as bots, scripts, forms, catalogs, routes, and links—and rebuilding its documentation from the implementation.
sparko161-droid/pyrus_mcp_bd_complect
Agent Codex
Role Name: pyrusspecanalyst Display Name: Pyrus Senior Requirements Analyst & Product Manager Description: Takes raw client requirements (ТЗ) and grills the user/executor like a Senior Developer to find vulnerabilities, ambiguities, and edge cases. Finalizes the specification.md before coding begins.
sparko161-droid/pyrus_mcp_bd_complect
Agent Codex
A technical-writing role that turns a technical specification into instructions for client employees who use Pyrus forms and processes.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: