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 OpenAEC-Foundation/OpenAEC-Workspace-Composer --skill solid-syntax-storesgit clone --depth 1 https://github.com/OpenAEC-Foundation/OpenAEC-Workspace-ComposerWrote 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/openaec-foundation/openaec-workspace-composer/solid-syntax-stores)<a href="https://agentmods.dev/skills/openaec-foundation/openaec-workspace-composer/solid-syntax-stores"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/solid-syntax-stores.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.00091 | $0.02608 |
| Opus 5 | $0.00046 | $0.01304 |
| Sonnet 5 | $0.00018 | $0.00522 |
| Haiku 4.5 | $0.00009 | $0.00261 |
Grade A, and why
solid-syntax-stores 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.
How it starts
The opening of the file, as written. The whole thing — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
solid-syntax-stores
Quick Reference
Import
// ALL store utilities come from "solid-js/store" — NEVER from "solid-js"
import { createStore, produce, reconcile, unwrap, createMutable } from "solid-js/store";
Store Primitives Overview
| Primitive | Purpose | Import |
|---|---|---|
createStore |
Proxy-based reactive state for nested data | solid-js/store |
setStore |
Path-syntax setter for surgical updates | Returned by createStore |
produce |
Immer-style mutation syntax | solid-js/store |
reconcile |
Data diffing for API responses | solid-js/store |
unwrap |
Strip reactive proxy to plain object | solid-js/store |
createMutable |
Direct mutation store (MobX/Vue-style) | solid-js/store |
Stores vs Signals Decision Tree
| Question | Use Signal | Use Store |
|---|---|---|
| Single primitive value (string, number, boolean)? | YES | NO |
| Nested object with multiple properties? | NO | YES |
| Array of objects that update individually? | NO | YES |
| Need fine-grained tracking per property? | NO | YES |
| Simple toggle or counter? | YES | NO |
| Form with many fields? | NO | YES |
| API response data (objects/arrays)? | NO | YES |
Rule of thumb: ALWAYS use createStore when your state is an object or array. ALWAYS use createSignal for primitives.
Stores vs Signals Syntax Comparison
| Aspect | Signal | Store |
|---|---|---|
| Create | const [val, setVal] = createSignal(0) |
const [store, setStore] = createStore({x: 0}) |
| Read | val() (function call) |
store.x (property access) |
| Write | setVal(1) |
setStore("x", 1) |
| Nested update | N/A | setStore("a", "b", "c", value) |
| Reactivity unit | Entire value | Per property |
Critical Warnings
NEVER destructure a store — it kills reactivity:
// WRONG — Reads value once, loses all reactive tracking
const { username } = store.users[0];
return <span>{username}</span>; // NEVER updates
// CORRECT — Access store properties in JSX directly
return <span>{store.users[0].username}</span>; // Fine-grained tracking
What ships with it
3 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 · 318 lines · 91 tokens per session scan A 34f15048294a
solid-syntax-stores is a skill published in the GitHub repository OpenAEC-Foundation/OpenAEC-Workspace-Composer (5 stars, last pushed 5mo ago), licensed MIT. It adds 91 tokens to every session and 2,608 once invoked, about $0.0005 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
massing-bim
Drive a Massing BIM/AEC project from an AI agent over MCP — read a project's status, records, CDE, KPI and model-quality checks; run standards-compliance, schedule-risk, embodied-carbon, permit- readiness and drawing-QA analyses; author the IFC model with GUID-stable recipes; and draft RFIs. Use when the user asks to…
ara3d-sdk
Use when processing AEC/BIM 3D data in .NET 8 — mesh generation and transformation, SIMD-accelerated math, IFC/STEP/PLY to glTF/GLB/VIM conversion, plugin development. Ara3D-SDK: high-performance .NET 3D geometry and BIM library suite.
elements
Use when generating building information models (BIM) programmatically in C#/.NET — wall, beam, column, floor creation, geometry kernel (BREP/CSG), glTF/IFC/JSON serialization, MEP systems, spatial grids. Hypar Elements: the smallest useful BIM — a cross-platform C# library for creating building elements without…
3d-skills
Use when working with 3D Gaussian Splatting (3DGS), .ply model cleanup/compression/publishing, interactive 360-degree panorama visualization and virtual tours, AEC/BIM 3D data processing, or CSG solid modeling. Index of 5 skills: SuperSplat, Photo-Sphere-Viewer, Ara3D-SDK, Elements, and OpenCSG.NET.
aios-arch
A workflow for reviewing software architecture, including service boundaries, technical choices, data and model boundaries, AI workflows, reliability, and long-term complexity.
aios-product
A product-management workflow for turning an approved direction into a defined software version with a product brief, priorities, acceptance measures, pilot or user-acceptance testing, and handover details.