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-core-reactivity-modelgit 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-core-reactivity-model)<a href="https://agentmods.dev/skills/openaec-foundation/openaec-workspace-composer/solid-core-reactivity-model"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/solid-core-reactivity-model/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/openaec-foundation/openaec-workspace-composer/solid-core-reactivity-model"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/solid-core-reactivity-model.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.00097 | $0.02428 |
| Opus 5 | $0.00048 | $0.01214 |
| Sonnet 5 | $0.00019 | $0.00486 |
| Haiku 4.5 | $0.00010 | $0.00243 |
Grade A, and why
solid-core-reactivity-model 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 9d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
solid-core-reactivity-model
Quick Reference
The Fundamental Mental Model
SolidJS has NO virtual DOM. Components run exactly once to set up a reactive dependency graph. Only reactive expressions (effects, memos, JSX bindings) re-execute when their dependencies change. The DOM is updated directly through reactive bindings — no diffing, no reconciliation, no re-rendering.
Tracking Scope Matrix
| Context | Tracking? | Re-executes on change? | Purpose |
|---|---|---|---|
createEffect(() => ...) |
YES | YES | Side effects |
createMemo(() => ...) |
YES | YES | Cached derived values |
createRenderEffect(() => ...) |
YES | YES | Synchronous render-phase effects |
createComputed(() => ...) |
YES | YES | Pre-render state sync |
JSX expression {count()} |
YES | YES | DOM text/attribute bindings |
| Component function body | NO | NO — runs once | Setup only |
Event handlers onClick |
NO | NO — runs on demand | User interaction |
onMount(() => ...) |
NO | NO — runs once after mount | DOM initialization |
untrack(() => ...) |
NO | NO — explicitly suppressed | Read without subscribing |
Reactive Dependency Graph
Signal (source) Memo (derived) Effect (sink)
[count] ──────────► [double] ──────────► [DOM update]
│ ▲
└──────────────────────────────────────────────┘
(direct subscription)
- Signals are sources — they store values and notify subscribers
- Memos are derived nodes — they cache computed values and propagate changes
- Effects are sinks — they perform side effects, NEVER produce reactive values
- Dependencies are tracked automatically when a signal/memo getter is called inside a tracking scope
Execution Models
| Aspect | SolidJS 1.x | SolidJS 2.x |
|---|---|---|
| Signal propagation | Synchronous — updates propagate immediately | Microtask-batched — reads reflect after flush |
| Forcing immediate propagation | N/A (already synchronous) | flush() |
| Effect timing | After render, before paint | Compute-then-apply split |
| Lifecycle hook | onMount |
onSettled (can return cleanup) |
| Async support | Manual via createResource |
First-class — computations can return Promises |
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.
- 9d ago First seen · 253 lines · 97 tokens per session scan A 78f939a824ef
solid-core-reactivity-model is a skill published in the GitHub repository OpenAEC-Foundation/OpenAEC-Workspace-Composer (5 stars, last pushed 5mo ago), licensed MIT. It adds 97 tokens to every session and 2,428 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
vue-debug-guides
Vue 3 debugging and error handling for runtime errors, warnings, async failures, and SSR/hydration issues. Use when diagnosing or fixing Vue issues.
error-tracking-svelte
PostHog error tracking for Svelte.
aios-arch-health
Deterministic architecture-health governance for repositories. Use when a project needs complexity, duplication, dependency, test, coverage, mutation, QA, performance, database, concurrency, or failure-injection evidence; evidence provenance and artifact digests; protected specification, test, quality-profile, or QA…
aios-exec
A controlled workflow for carrying out clearly defined changes and checks in a project workspace. It covers code, bug fixes, documentation, scripts, tests, linting, type checks, builds, interface changes, and deployment preparation.
threejs-errors-rendering
Use when a Three.js scene renders incorrectly: black screen, invisible objects, wrong colors, z-fighting, or broken shadows. Prevents the common mistake of wrong color space, missing material.side, or forgetting updateProjectionMatrix. Covers all common rendering errors with diagnosis steps and fix patterns. Keywords…
vite-mcp-next
Use when debugging Vite + Vue local pages with vite-plugin-vue-mcp-next MCP, including DOM, screenshots, console logs, network requests, Vue components, router, or Pinia state.