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 korbinjoe/TeemAI --skill dev-servergit clone --depth 1 https://github.com/korbinjoe/TeemAIWrote 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/korbinjoe/teemai/dev-server)<a href="https://agentmods.dev/skills/korbinjoe/teemai/dev-server"><img src="https://agentmods.dev/badge/skills/korbinjoe/teemai/dev-server/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/korbinjoe/teemai/dev-server"><img src="https://agentmods.dev/badge/skills/korbinjoe/teemai/dev-server.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.00041 | $0.00476 |
| Opus 5.5 | $0.00016 | $0.00190 |
| Sonnet 5.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 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.
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.
- 1mo 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 3mo ago), licensed MIT. It adds 41 tokens to every session and 476 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
managing-mcp-servers
Use when the user asks to add, change, remove, enable or disable an MCP server, or when an MCP tool is missing, needs sign-in, fails, or was blocked. ThinkRail runs pi in-process, so there is no pi command to call.
todos
Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.
asking-user-questions
Use when composing an askuserquestion round inside a workflow, or when a workflow skill names it at a question step. Shared norms for the tool — not a workflow, nothing to execute.
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
writing-specs
Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.
setting-up-a-project
Use when asked to set up, onboard, initialize, or spec a project with no spec graph, or when invoked by the app's Set-up-project card. Not for ordinary work in an already-specced project.