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 pantheon-org/tekhne --skill vite-integrationgit clone --depth 1 https://github.com/pantheon-org/tekhneWrote 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/pantheon-org/tekhne/vite-integration)<a href="https://agentmods.dev/skills/pantheon-org/tekhne/vite-integration"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/vite-integration/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/pantheon-org/tekhne/vite-integration"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/vite-integration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00220 | $0.01777 |
| Opus 5 | $0.00110 | $0.00889 |
| Sonnet 5 | $0.00044 | $0.00355 |
| Haiku 4.5 | $0.00022 | $0.00178 |
Grade A, and why
nx-vite-integration 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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nx Vite Integration
Configure Vite as the build tool in Nx workspaces with predictable, cache-friendly defaults.
Mindset
Nx and Vite each have their own opinions about project structure. The integration works by making Vite defer to Nx for path resolution and task orchestration while Nx defers to Vite for bundling. The critical bridge is nxViteTsPaths() — without it, workspace path aliases silently resolve to nothing and builds fail with cryptic module-not-found errors.
Think in two layers: workspace-level (Nx executor targets, cache dirs, project boundaries) and build-level (Vite plugins, rollup options, output formats). Workspace-level decisions live in project.json; build-level decisions live in vite.config.ts. Keep them separate and each layer becomes predictable.
Library mode differs meaningfully from app mode: apps bundle everything together, libraries externalize peer deps to avoid duplication in consumers. The distinction determines whether rollupOptions.external and vite-plugin-dts are needed.
When to Use
| Scenario | Use This Skill |
|---|---|
| Adding Vite to an existing Nx app or lib | Yes |
| Migrating from Webpack or CRA to Vite inside Nx | Yes |
| Setting up Vitest alongside an existing Vite config | Yes |
Fixing @org/lib path aliases failing in Vite builds |
Yes |
Configuring library mode (build.lib) with DTS output |
Yes |
| Setting up a standalone Vite project (no Nx) | No — use Vite docs directly |
| Adding a non-Vite bundler (esbuild standalone, Rollup) | No — this skill is Nx + Vite specific |
Workflow
Step 1: Install Dependencies
Preconditions:
- Nx workspace exists
- Node.js 18+ and package manager available
Commands:
bunx nx add @nx/vite
bun add -d vite
Framework plugin (choose one):
bun add -d @vitejs/plugin-react
# or
bun add -d @vitejs/plugin-vue
# or
bun add -d @sveltejs/vite-plugin-svelte
Expected result:
@nx/viteand framework plugin installed
Step 2: Generate or Configure Vite
What ships with it
24 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.
- .audits/2026-02-21/analysis.md 8.1 KB
- .audits/2026-02-21/audit.json 144 B
- .audits/2026-02-21/remediation-plan.md 234 B
- .audits/2026-02-22/analysis.md 8.1 KB
- .audits/2026-02-22/audit.json 144 B
- .audits/2026-02-22/remediation-plan.md 234 B
- .audits/2026-02-23/analysis.md 2.0 KB
- .audits/2026-02-23/audit.json 142 B
- .audits/2026-02-23/remediation-plan.md 230 B
- .audits/2026-03-02/analysis.md 1.0 KB
- .audits/2026-03-02/audit.json 414 B
- .audits/2026-03-02/remediation-plan.md 2.3 KB
- .audits/latest 10 B
- .tessl-plugin/plugin.json 1.0 KB
- CHANGELOG.md 736 B
- evals/scenario-01.md 2.8 KB
- evals/scenario-02.md 3.3 KB
- evals/scenario-03.md 3.3 KB
- evals/scenario-04.md 3.6 KB
- references/library-mode-guide.md 1.4 KB
- references/nx-vite-plugin-reference.md 1.4 KB
- references/troubleshooting.md 1.6 KB
- references/vite-config-patterns.md 2.4 KB
- references/vitest-integration.md 1.1 KB
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 · 274 lines · 220 tokens per session scan A b8b00e134552
nx-vite-integration is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed yesterday), licensed MIT. It adds 220 tokens to every session and 1,777 once invoked, about $0.0011 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-09-03.
Other skills, from other repositories
diff
Reconcile a converted/built web page against its source prototype with two complementary probes — a PIXEL/layout diff (stretched images, dropped wraps, blank renders, colour flips) and a STRUCTURAL content+typography diff (dropped/mis-slotted headings, eyebrows, CTAs; rendered-face font forks). Stack-agnostic via…
find-test-content
Use this when you need to find existing pages that already use a specific block in an AEM Edge Delivery Services project, for example to locate test content or examples during block development. Covers reporting page URLs with occurrence counts and block variants. This searches existing content; to import a new page…
frontend-testing
Comprehensive frontend testing strategy covering unit, integration, E2E, visual regression, and accessibility testing.
accessibility-testing
WCAG 2.1/2.2 audit, axe, Lighthouse, manual testing, screen reader testing, and remediation.
appbuilder-testing
Generate and run tests for Adobe App Builder actions and UI components. Scaffolds Jest unit tests, integration tests against deployed actions, contract tests for Adobe API interactions, and React component tests using Testing Library. Provides mock helpers for State, Files, Events SDKs, @adobe/aio-lib- clients, ExC…
visual-qa-vision-agent
Equips the AI agent with visual QA capabilities using Playwright/Puppeteer and the agent's innate Vision capabilities to self-correct UI layout, CSS alignment, and visual regressions.