eve is a filesystem-first framework for building durable AI agents, with agent instructions, tools, and configuration kept in ordinary project files. It is for developers creating agents that can be inspected, extended, and operated through a conventional codebase. The catalogue add-ons support working with eve agents and their workflows.
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 vercel/eve --skill dashboard-chat-best-practicesgit clone --depth 1 https://github.com/vercel/eveWrote 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/vercel/eve/dashboard-chat-best-practices)<a href="https://agentmods.dev/skills/vercel/eve/dashboard-chat-best-practices"><img src="https://agentmods.dev/badge/skills/vercel/eve/dashboard-chat-best-practices/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/vercel/eve/dashboard-chat-best-practices"><img src="https://agentmods.dev/badge/skills/vercel/eve/dashboard-chat-best-practices.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.00084 | $0.01706 |
| Opus 5.5 | $0.00034 | $0.00682 |
| Sonnet 5.5 | $0.00017 | $0.00341 |
| Haiku 4.5 | $0.00008 | $0.00171 |
Grade A, and why
dashboard-chat-best-practices 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 1mo 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dashboard Chat Best Practices
Overview
Use this skill to keep the template's web chat feeling like a polished dashboard surface: stable, quiet, fast to first paint, and predictable under streaming state.
Product Shape
- Build the actual chat surface, not a marketing page. The first screen should be a usable composer, sidebar, or chat route.
- Keep the aesthetic restrained and work-focused: dense but readable spacing, quiet borders, predictable controls, and minimal decoration.
- Prefer existing shadcn/Tailwind primitives and local components over new abstractions.
- Use icons for compact commands, with accessible labels/tooltips. Avoid explanatory in-app text for behavior that good controls can imply.
Cache Components And PPR Basics
- Keep
cacheComponents: trueenabled innext.config.ts. Treat the chat route as a static shell with dynamic data streamed into Suspense boundaries. - Keep the shell cheap and deterministic. Do not make
app/(chat)/layout.tsxwait on auth, database, chat history, or per-chat data before rendering the shell. - Pass cheap initial state into
AgentChatShell: empty history,initialNextCursor: null,viewer: null, andgetInitialSetupStatus(). - Load expensive or request-bound data inside hidden Suspense children:
ResolvedChatBootstrapfor setup/viewer/sidebar history andExistingChatfor active chat data. - Use sync components to hand resolved server data to the client shell.
AgentChatBootstrapSyncshould update setup status, viewer, and history.AgentChatRouteSyncshould update the active chat for the current route. - Keep Suspense fallbacks
nullfor these sync boundaries when the visible shell already has stable placeholders. Do not add loading panels that push the chat frame around. - Do not call
notFound()until the dynamic boundary has enough real viewer/setup/chat data to prove the chat is inaccessible. The outer shell should still render while that decision is loading. - Keep root and session routes visually distinct but structurally compatible. The root page can center the composer; the session page can pin it near the bottom. Both should live inside the same shell.
- Treat PPR/static shell work as a latency feature and a correctness feature. The goal is first paint without auth/database blocking, then precise data reconciliation after bootstrap.
What ships with it
1 file 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.
- 1mo ago First seen · 90 lines · 84 tokens per session scan A d9477b786d5c
dashboard-chat-best-practices is a skill published in the GitHub repository vercel/eve (5,573 stars, last pushed today), licensed Apache-2.0. It adds 84 tokens to every session and 1,706 once invoked, about $0.0003 per session on Opus 5.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-15.
Other skills, from other repositories
frontmcp-guides
Tutorials, end-to-end walkthroughs, and complete reference projects for FrontMCP. Use when you want a getting-started guide, a full worked example, or to learn best practices by following a step-by-step build rather than a single API reference. Includes a beginner weather-API server (tool plus static resource, Zod…
create-skill
Create instruction-only skills that package knowledge and workflow guides for AI clients.
frontmcp-extensibility
Use when extending FrontMCP beyond the core SDK by integrating external npm packages, libraries, or third-party services into providers and tools. Covers VectoriaDB for in-memory semantic and vector search (ML-based embeddings or TF-IDF keyword engines, with persistence) and the tamper-evident, hash-chained skill…
incident-response-skill
A skill that uses object-style tool references with purpose descriptions and required flags, plus strict validation.
parameterized-skill
A skill with customizable parameters, usage examples for AI guidance, and controlled visibility.
basic-inline-skill
A minimal instruction-only skill with inline content and the function builder alternative.