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 Elnora-AI/elnora-ai-agent-hackathon-starter-kit --skill setupgit clone --depth 1 https://github.com/Elnora-AI/elnora-ai-agent-hackathon-starter-kitWrote 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/elnora-ai/elnora-ai-agent-hackathon-starter-kit/setup)<a href="https://agentmods.dev/skills/elnora-ai/elnora-ai-agent-hackathon-starter-kit/setup"><img src="https://agentmods.dev/badge/skills/elnora-ai/elnora-ai-agent-hackathon-starter-kit/setup.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.1 | $0.00024 | $0.00420 |
| Opus 5 | $0.00012 | $0.00210 |
| Sonnet 5 | $0.00005 | $0.00084 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
setup 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 7d 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
Vercel Setup
First-time setup: install CLI, authenticate, link project, pull environment variables.
Steps
1. Install Vercel CLI
vercel --version 2>/dev/null || npm i -g vercel
2. Authenticate
vercel login
Follow the browser prompt to complete authentication.
3. Link project
Single project (most cases):
vercel link
Monorepo with multiple Vercel projects:
vercel link --repo
Monorepo decision: if the repo has multiple apps each deployed separately (e.g., apps/web, apps/api), use --repo. Otherwise, vercel link is fine.
4. Verify linking
cat .vercel/project.json 2>/dev/null || cat .vercel/repo.json 2>/dev/null
5. Pull environment variables
vercel pull
This creates .vercel/.env.development.local with your project's env vars.
6. Verify setup
vercel whoami && vercel project ls
Post-Setup
- Run
vercel devto start local development with Vercel's serverless functions. - Run
vercel deployfor a preview deployment. - See
references/getting-started.mdandreferences/environment-variables.mdfor details.
Anti-Patterns
- Don't let commands auto-link in monorepos — always run
vercel link(or--repo) explicitly first. - Don't link while on the wrong team — check with
vercel whoami, switch withvercel teams switch.
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.
- 7d ago First seen · 65 lines · 24 tokens per session scan A 525435cdcd86
setup is a skill published in the GitHub repository Elnora-AI/elnora-ai-agent-hackathon-starter-kit (22 stars, last pushed today), licensed Apache-2.0. It adds 24 tokens to every session and 420 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
merge-seed
Merge upstream React Starter Kit updates (the seed remote) into main, preserving this project's identity, scope, and behavior. Use when asked to sync, pull, or merge the seed / starter kit / upstream template.
vite-tunnel
A guide for exposing a local Vite development server through a Cloudflare Named Tunnel, giving it a stable public web address.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json…
deploy-to-vercel
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).