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 skills/deeleeramone/pywry/component_referencenpx skills add deeleeramone/PyWry --skill component_referencegit clone --depth 1 https://github.com/deeleeramone/PyWryWhat 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.00000 | $0.08147 |
| Opus 5 | $0.00000 | $0.04074 |
| Sonnet 5 | $0.00000 | $0.01629 |
| Haiku 4.5 | $0.00000 | $0.00815 |
Grade A, and why
component_reference 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 2d 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 — 1,024 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PyWry Component Reference - MANDATORY SYNTAX
STOP. THIS IS THE AUTHORITATIVE REFERENCE FOR ALL COMPONENTS. YOU MUST USE THE EXACT EVENT SIGNATURES DOCUMENTED HERE. THERE ARE NO EXCEPTIONS. NO WORKAROUNDS. NO DEVIATIONS.
CRITICAL: System Events for Widget Updates
These are the ONLY events that work for updating widgets. Use send_event tool with these event types:
AG Grid Data Updates
| Event Type | Payload | Description |
|---|---|---|
grid:update-data |
{"data": [...rows...], "strategy": "set"} |
Replace all rows |
grid:update-data |
{"data": [...rows...], "strategy": "append"} |
Append rows |
grid:update-data |
{"data": [...rows...], "strategy": "update"} |
Update existing rows |
grid:update-columns |
{"columnDefs": [...]} |
Update column definitions |
grid:update-cell |
{"rowId": "row-1", "colId": "price", "value": 99.50} |
Update single cell |
AG Grid State Persistence
| Event Type | Payload | Description |
|---|---|---|
grid:request-state |
{} |
Request current grid state |
grid:request-state |
{"gridId": "my-grid"} |
Request specific grid's state |
grid:restore-state |
{"state": {...savedState...}} |
Restore saved grid state |
grid:reset-state |
{"hard": false} |
Soft reset (keeps column order) |
grid:reset-state |
{"hard": true} |
Hard reset (full reset) |
Response Event: grid:state-response with {"gridId": "...", "state": {...}}
State Object Contents:
- Column state (width, order, visibility, pinned, sort)
- Filter state (active filters per column)
- Sort state (sorted columns and direction)
Plotly Chart Updates
| Event Type | Payload | Description |
|---|---|---|
plotly:update-figure |
{"data": [...], "layout": {...}} |
Full figure update |
plotly:update-layout |
{"layout": {...}} |
Layout only update |
plotly:reset-zoom |
{} |
Reset chart zoom to original |
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.
- 2d ago First seen · 1,024 lines · 0 tokens per session scan A fba49cddcc32
component_reference is a skill published in the GitHub repository deeleeramone/PyWry (93 stars, last pushed 8d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 8,147 tokens. 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 skills, from other repositories
dashboard-design
Use this skill first when the user wants to design or plan a dashboard, especially Vizro dashboards. Enforces a 3-step workflow (requirements, layout, visualization) before implementation. Activate when the user asks to create, design, or plan a dashboard. For implementation, use the dashboard-build skill after…
industry-chain
产业链下钻与不可替代性判定方法:以龙头为"需求入口"沿供应链逐层下钻(整机 / 龙头 → 部件 → 核心器件 → 材料 → 衬底与设备),用物理 / 材料约束(扩产周期、良率、认证周期、有无替代)当筛子找供给刚性的卡口;给每个标的贴不可替代性标签(techmoat / capacitymoat / both / 待补)并列证据;含"卡口越硬越贵"与预期差四问的校准。当任务涉及产业链位置、上下游、护城河、不可替代性、供给瓶颈、竞争格局时加载;单纯取数、估值计算、财报拆分等不涉及产业链结构的任务不要加载。只产出框架与证据表,不给投资动作建议。.
live-dashboard
Notion 风团队仪表板, KPI + 7 日 sparkline + activity feed + 任务表.
selecting-vizro-charts
Use this skill when choosing chart types, applying Plotly Express conventions, configuring colors, building KPI cards, or adding tables (AG Grid) to Vizro dashboards. Activate when the user asks which chart fits their data, needs custom chart functions, wants to set colors or palettes, is creating KPI metric cards, or…
verify-changes
Verify a code change in this repo before committing or opening a PR. Use after editing collector (backend), web (frontend), shared package, or the Go agent — picks the minimal sufficient check set per touched area.
openai-docs
Use when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations (for example: Codex, Responses API, Chat Completions, Apps SDK, Agents SDK, Realtime, model capabilities or limits); prioritize OpenAI docs MCP tools and restrict any fallback browsing to…