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/korbinjoe/teemai/dev-servernpx skills add korbinjoe/TeemAI --skill dev-servergit clone --depth 1 https://github.com/korbinjoe/TeemAIWhat 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.00041 | $0.00476 |
| Opus 5 | $0.00020 | $0.00238 |
| Sonnet 5 | $0.00008 | $0.00095 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
dev-server 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 2d 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
Dev Server Management
Manage local dev servers via Bash commands.
Check Dev Server Status
# Check if a service is running on a specific port
lsof -i :<port> -t 2>/dev/null
If there's output (PID), a service is running on that port. URL: http://localhost:<port>.
If unsure about the port, scan common ports:
for port in 5173 3000 3001 8080; do
if lsof -i :$port -t 2>/dev/null > /dev/null; then
echo "Dev server running on port $port → http://localhost:$port"
fi
done
Start Dev Server
# Start in background (default: npm run dev)
npm run dev &
# Wait for service to be ready (max 15 seconds)
for i in $(seq 1 30); do
if lsof -i :5173 -t 2>/dev/null > /dev/null; then
echo "Dev server ready → http://localhost:5173"
break
fi
sleep 0.5
done
If the port is already occupied, no need to start again — use the existing service.
Get Dev Server URL
Scan common ports and return the first running service URL:
for port in 5173 3000 3001 8080; do
if lsof -i :$port -t 2>/dev/null > /dev/null; then
echo "http://localhost:$port"
break
fi
done
Best Practices for Determining the Port
- Read
server.portconfig fromvite.config.tsorvite.config.js - If no explicit config, Vite defaults to port
5173 - If default port is occupied, Vite auto-increments (5174, 5175...)
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.
- 2d ago First seen · 68 lines · 41 tokens per session scan A 76067624d44f
dev-server is a skill published in the GitHub repository korbinjoe/TeemAI (2 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 476 once invoked, about $0.0002 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
frontman-dev
AI-powered visual frontend editing in your browser. Click any element in your running app, describe changes in plain English, and get real source file edits with instant hot reload. Works with Next.js, Astro, and Vite.
frontman-agent-usage
Use this skill when an agent needs to explain or operate Frontman's browser-aware frontend coding workflow.
frontman-installation
Use this skill when helping a developer install Frontman in a web project.
frontman-site-navigation
Use this skill when an agent needs to find Frontman product, documentation, legal, support, or discovery resources.
computer-and-browser
Route desktop and browser work across an isolated browser, the harness's own Chrome extension (Claude in Chrome, the Codex Chrome plugin, or the bundled Agent Browser MCP) on the signed-in Chrome profile, and Peekaboo computer use. Use when the user asks for computer use, desktop control, existing Chrome, signed-in…
Read and act on Reddit through the signed-in Chrome session on the shared computer. Use page-level browser tools only. Open old.reddit.com URLs for inbox, user, listings, search, and threads. Write (comment, post, vote, message) only when the user explicitly asks.