Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/OpenAEC-Foundation/OpenAEC-Workspace-Composernpx agentmods add skills/openaec-foundation/openaec-workspace-composer/solid-agents-project-scaffolderWrote 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-agents-project-scaffolder)<a href="https://agentmods.dev/skills/openaec-foundation/openaec-workspace-composer/solid-agents-project-scaffolder"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/solid-agents-project-scaffolder/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-agents-project-scaffolder"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/solid-agents-project-scaffolder.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.00099 | $0.02885 |
| Opus 5 | $0.00049 | $0.01443 |
| Sonnet 5 | $0.00020 | $0.00577 |
| Haiku 4.5 | $0.00010 | $0.00288 |
Grade A, and why
solid-agents-project-scaffolder 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 10d 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 — 431 lines — stays where its author put it; the contents beside it link to each section on GitHub.
solid-agents-project-scaffolder
Quick Reference
Project Type Decision Tree
Need a new SolidJS project?
├── Need SSR, file-based routing, server functions, or API routes?
│ └── YES → SolidStart scaffold
│ ├── Full-stack app with data loading? → SolidStart with query/action
│ ├── Static site with prerendering? → SolidStart with SSG preset
│ └── API backend + frontend? → SolidStart with API routes
└── NO → Plain SolidJS scaffold (client-side SPA)
├── Simple reactive UI? → Plain SolidJS + Vite
├── Need routing? → Plain SolidJS + @solidjs/router
└── Embedded widget or library? → Plain SolidJS minimal
Critical Warnings
NEVER use create-react-app, next, or any React scaffolding tool for a SolidJS project. The generated configuration, babel presets, and JSX transform are incompatible.
NEVER omit vite-plugin-solid from vite.config.ts. Without it, JSX compilation fails silently or produces React output.
ALWAYS set "jsxImportSource": "solid-js" in tsconfig.json. Without this, TypeScript resolves JSX types from React, causing type errors on SolidJS-specific attributes.
ALWAYS use babel-preset-solid (included via vite-plugin-solid). This preset compiles JSX into SolidJS's fine-grained reactive DOM operations instead of React.createElement calls.
NEVER include react, react-dom, @types/react, or @types/react-dom in dependencies. Their presence causes type conflicts and import confusion.
ALWAYS use solid-js/web for render and hydrate — these are NOT imported from solid-js directly.
Plain SolidJS Scaffold (Client-Side SPA)
Required Dependencies
| Package | Type | Purpose |
|---|---|---|
solid-js |
dependency | Core reactive framework |
@solidjs/router |
dependency | Client-side routing (if needed) |
typescript |
devDependency | TypeScript compiler |
vite |
devDependency | Build tool and dev server |
vite-plugin-solid |
devDependency | Vite integration for SolidJS JSX compilation |
vitest |
devDependency | Testing framework |
@solidjs/testing-library |
devDependency | Component testing utilities |
jsdom |
devDependency | DOM environment for tests |
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.
- 10d ago First seen · 431 lines · 99 tokens per session scan A ea6fac116930
solid-agents-project-scaffolder is a skill published in the GitHub repository OpenAEC-Foundation/OpenAEC-Workspace-Composer (5 stars, last pushed 5mo ago), licensed MIT. It adds 99 tokens to every session and 2,885 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
panel-app-creator
Create or update the Panel UI component of a complete schema v2 NextClaw Mini App or an explicitly loose local Panel. Use after nextclaw-app-creator selects Panel-only or Panel + Service, or for right-side UI, Service Actions, Agent-powered panels, React/Vite panels, and App bridge capability questions.
gemigo-cli
Use when the user wants to publish an already-built static website or front-end app through GemiGo, such as a Vite/React/Vue static build, plain HTML/CSS/JS page, landing page, demo, docs site, or small browser app, and get a hosted public URL.
impeccable
Use when the user wants distinctive, production-grade frontend design, anti-generic AI aesthetics, UX critique, technical UI audits, or final polish through bundled Impeccable references and an optional upstream detector CLI.
color-palette-generator
Create an HTML color palette from a mood, description, or image, with swatches, color codes, pairings, and contrast checks. Use for color schemes or brand colors.
ui-ux-pro-max
Use when the user wants professional UI/UX design guidance, design-system generation, UX review, or stack-specific frontend guidance through a bundled local UI/UX Pro Max dataset and Python search runtime.
panel-app-react-vite-creator
Create or update an engineering-style NextClaw Panel component with pnpm, Vite, React, TypeScript, and Tailwind CSS, then build it into a static .panel directory inside a schema v2 package or an explicitly loose workspace Panel. Use for modern, reusable, complex, Agent-powered, typed Panel interfaces.