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 nxtg-ai/forge-plugin --skill dev-environment-patternsgit clone --depth 1 https://github.com/nxtg-ai/forge-pluginWrote 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/nxtg-ai/forge-plugin/dev-environment-patterns)<a href="https://agentmods.dev/skills/nxtg-ai/forge-plugin/dev-environment-patterns"><img src="https://agentmods.dev/badge/skills/nxtg-ai/forge-plugin/dev-environment-patterns/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/nxtg-ai/forge-plugin/dev-environment-patterns"><img src="https://agentmods.dev/badge/skills/nxtg-ai/forge-plugin/dev-environment-patterns.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.00105 | $0.02176 |
| Opus 5.5 | $0.00042 | $0.00870 |
| Sonnet 5.5 | $0.00021 | $0.00435 |
| Haiku 4.5 | $0.00011 | $0.00218 |
Grade A, and why
Dev Environment Patterns scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Read, Grep, Bash(lsof:*), Bash(ss:*), Bash(curl:*), Bash(cat:*) How it starts
The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Environment Patterns
Institutional knowledge for local dev-server networking, learned from real
forge-ui debugging. All code here mirrors the live config in
forge-ui/vite.config.ts and forge-ui/src/services/api-client.ts (ports:
UI 5050 → proxies to API/WS 5051).
Pattern: Multi-Device Development Access
Severity: Critical (blocks all functionality from non-localhost devices).
Symptom
API/WS calls fail only when accessed from a phone, tablet, or another PC:
Cross-Origin Request Blocked: localhost:5051NetworkError when attempting to fetch resource- WebSocket connection failures
Root cause
localhost on the remote device points at that device, not the dev server.
Any URL that names localhost (hardcoded or via VITE_API_URL) is unreachable
off-machine. The fix is relative URLs proxied by Vite, so the browser only ever
talks same-origin to whatever host it loaded the page from.
Correct pattern (matches live source)
// src/services/api-client.ts — env var wins, else relative /api in dev
const getApiBaseUrl = () => {
if (import.meta.env.VITE_API_URL) return import.meta.env.VITE_API_URL; // prod only
if (import.meta.env.DEV) return "/api"; // Vite proxies this
const host = typeof window !== "undefined" ? window.location.hostname : "localhost";
return `http://${host}:5051/api`; // prod fallback
};
// vite.config.ts — bind all interfaces + proxy /api, /ws, /terminal to 5051
server: {
host: "0.0.0.0", // accept connections from any device
port: 5050,
strictPort: true, // FAIL if taken — does NOT auto-increment
proxy: {
"/api": { target: "http://localhost:5051", changeOrigin: true },
"/ws": { target: "ws://localhost:5051", ws: true, changeOrigin: true },
"/terminal": { target: "ws://localhost:5051", ws: true },
},
}
# .env — never hardcode localhost. Leave VITE_API_URL UNSET in dev.
# VITE_API_URL=http://localhost:5051/api # WRONG — breaks every non-local device
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.
- 3d ago Changed 0f8e757f2005
- 1mo ago First seen · 173 lines · 105 tokens per session scan A c720d8b61251
Dev Environment Patterns is a skill published in the GitHub repository nxtg-ai/forge-plugin (6 stars, last pushed 4d ago), licensed MIT. It adds 105 tokens to every session and 2,176 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
dev
One-command dev loop boot. Spins up portless (named HTTPS subdomain), emulate (stateful API mocks), the project's dev server, and an agent-browser session, all keyed to the current git branch. Use when starting a feature branch, switching worktrees, or returning to a project after a break. Skips silently with install…
flyio
Version: 1.0.0 | Target Size: <25KB | Purpose: Fast reference for Fly.io deployments and global application distribution.
aws-cloud
Quick reference for AWS infrastructure automation with Terraform, security-first design, and production-ready patterns.
managing-supabase
Supabase CLI for database management, Edge Functions, migrations, and local development. Use for managing Postgres databases, deploying serverless functions, and debugging Supabase projects.
managing-railway
Railway platform CLI for service deployment, infrastructure management, and debugging. Use for creating services, managing deployments, configuring networking, and reviewing logs.
managing-vercel
Vercel platform CLI for frontend deployments, serverless functions, and edge network management. Use for deploying applications, managing domains, environment variables, and debugging deployments.