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/demondamon/agenticx/scaffold-vite-reactnpx skills add DemonDamon/AgenticX --skill scaffold-vite-reactgit clone --depth 1 https://github.com/DemonDamon/AgenticXWrote 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/demondamon/agenticx/scaffold-vite-react)<a href="https://agentmods.dev/skills/demondamon/agenticx/scaffold-vite-react"><img src="https://agentmods.dev/badge/skills/demondamon/agenticx/scaffold-vite-react.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 | $0.00022 | $0.00212 |
| Opus 5 | $0.00011 | $0.00106 |
| Sonnet 5 | $0.00004 | $0.00042 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
scaffold-vite-react 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 5d 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.
What it actually says
Scaffold Vite + React POC
Output location
output/<task_id>/frontend/ inside the delivery worktree.
Steps
pnpm create vite@latest . --template react-ts(or equivalent) in frontend dir- Add React Router for routes from requirement-breakdown.md
- Wire semantic CSS variables matching design-system.md
- Mock data only — no real API unless specified
Pages
Implement every route listed in requirement breakdown:
- Dashboard
- Task list (if applicable)
- Settings (if applicable)
Verification
pnpm install && pnpm buildsucceeds- README.md documents dev command and port
Constraints
- Do not modify AgenticX core packages
- Keep dependencies minimal (react, react-router-dom, vite)
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.
- 5d ago First seen · 39 lines · 22 tokens per session scan A 5f3b8af0925c
scaffold-vite-react is a skill published in the GitHub repository DemonDamon/AgenticX (227 stars, last pushed today), licensed Apache-2.0. It adds 22 tokens to every session and 212 once invoked, about $0.0001 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-30.
Other skills, from other repositories
weather
Get current weather and forecasts (no API key required).
github
Interact with GitHub using the gh CLI. Use gh issue, gh pr, gh run, and gh api for issues, PRs, CI runs, and advanced queries.
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.
continuum-tools-mcp
Connect MCP servers (Stdio/SSE/StreamableHTTP) to a Continuum agent, configure tool filtering, set up tool-context capture/injection (e.g. sessionid), and read run artifacts (UI widgets, structured tool data). Invoke when the user asks "connect MCP", "filesystem tool", "remote API tool", "auto-capture sessionid"…
continuum-handoffs
Build agent-to-agent transitions with Continuum's Handoff system — triage routing, history summarization modes (FULL/SUMMARY/RECENTN/HYBRID), cycle detection, depth tracking, return-to-parent. Invoke when the user asks "route customer requests to specialists", "agent that can transfer to another", "summarize history…
continuum-llm-providers
Pick the right LLM provider, configure structured outputs, control context-window compression, and use the LLMClient directly. Provider routing is by model-string prefix; LiteLLM has been removed. Also covers Smart Gateway integration for multi-provider routing. Invoke when the user asks about "switch to Claude"…