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 pedroiff0/awesome-skills --skill docker-single-port-multi-instancegit clone --depth 1 https://github.com/pedroiff0/awesome-skillsWrote 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/pedroiff0/awesome-skills/docker-single-port-multi-instance)<a href="https://agentmods.dev/skills/pedroiff0/awesome-skills/docker-single-port-multi-instance"><img src="https://agentmods.dev/badge/skills/pedroiff0/awesome-skills/docker-single-port-multi-instance/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/pedroiff0/awesome-skills/docker-single-port-multi-instance"><img src="https://agentmods.dev/badge/skills/pedroiff0/awesome-skills/docker-single-port-multi-instance.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.00073 | $0.01849 |
| Opus 5 | $0.00036 | $0.00924 |
| Sonnet 5 | $0.00015 | $0.00370 |
| Haiku 4.5 | $0.00007 | $0.00185 |
Grade A, and why
docker-single-port-multi-instance 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 8d 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.
Verify with `curl -s -D - -o /dev/null URL/demo | grep -i location` — it must How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
One port, many instances: nginx reverse proxy by path prefix
When this applies
- You have an app that runs as several instances: production, test, and a public demo — each with its OWN database.
- The user asks for a single published port (e.g. 4460) where the demo is reached by clicking a button on the landing page, and the demo's data lives in its own DB, isolated from prod/test.
- Key constraint: the demo must be reachable SIMULTANEOUSLY with the main app.
Prefer nginx-by-prefix over in-app multi-tenancy
When the ONLY goal is routing separate instances, do NOT refactor the app to hold two DB connections (e.g. a second mongoose connection) just to serve /demo/* from the same process. That touches ~30 files (every model + service + controller) and risks regressing the normal routes. Instead:
- Keep each instance as its own container (own DB, own env).
- Put ONE nginx container on the public port; it routes:
/demo/*→app-demo(strip prefix:proxy_pass http://app-demo:5000/;)/(rest) →app(the principal: test or prod chosen via .env)
- The demo container keeps its existing autologin; the button on the landing
just points to
/demo/app.
This delivers "one port, demo with own DB, simultaneous" with near-zero risk to the main app's logic.
The non-obvious gotcha: APIs must also be prefixed
If the demo is served under /demo/* but its client JS calls /api/...
(absolute), the proxy sends those calls to the PRINCIPAL instance, not the
demo → tokens fail (401 "Token invalido"). You must route the demo's APIs to
the demo instance too:
- Mount the demo's API router under
/demo/apiin the app (only when a DEMO_AUTOLOGIN-style flag is set), in addition to the normal/api. - Make the frontend prefix API calls with
/demowhen running in the demo. Inject the prefix WITHOUT an inline script (CSP will block it — see the express-csp-runtime-config skill): usedata-api-prefix="/demo"on<html>and read it withgetAttributeinside the shared fetch wrapper.
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.
- 8d ago First seen · 134 lines · 73 tokens per session scan A c07565c7c5a3
docker-single-port-multi-instance is a skill published in the GitHub repository pedroiff0/awesome-skills (1 stars, last pushed yesterday), licensed MIT. It adds 73 tokens to every session and 1,849 once invoked, about $0.0004 per session on Opus 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-08-31.
Other skills, from other repositories
review-test-refactoring
Review PyTorch test refactoring for correctness and completeness against the decoupling standards defined in the refactor-test-decoupling skill. Accepts a test file path (whole-file review), a PR URL, a git diff, or a branch name. Use this when asked to review a test refactoring PR, check a test decoupling change…
accessibility-testing-best-practices
Use when applying accessibility testing best practices.
accessibility-testing-implementation
Use when applying accessibility testing implementation.
accessibility-testing-axe
Use when testing accessibility with axe.
specification-compliance-review
Use this skill when an implementation is described as partial, passing, or complete and the task is to determine whether it actually satisfies an explicit specification. This is not a generic code review and not a re-run of the test suite. The central question is: does every normative requirement have both a correct…
review-prs
Review a GitHub pull request in the googleapis/mcp-toolbox repo against the team's reviewer checklist: PR title/description conventions, linked issue, logic errors and unhandled edge cases, breaking changes, test coverage, docs updates, security (input handling), and new dependencies. Use whenever a maintainer asks…