Borrowing it
Nothing to install: this file belongs to hoangsonww/WealthWise-Finance-Tracker. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hoangsonww/WealthWise-Finance-Tracker/master/.agents/skills/docker-up/SKILL.mdgit clone --depth 1 https://github.com/hoangsonww/WealthWise-Finance-TrackerWrote 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/hoangsonww/wealthwise-finance-tracker/docker-up)<a href="https://agentmods.dev/skills/hoangsonww/wealthwise-finance-tracker/docker-up"><img src="https://agentmods.dev/badge/skills/hoangsonww/wealthwise-finance-tracker/docker-up/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/hoangsonww/wealthwise-finance-tracker/docker-up"><img src="https://agentmods.dev/badge/skills/hoangsonww/wealthwise-finance-tracker/docker-up.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.00056 | $0.00842 |
| Opus 5 | $0.00028 | $0.00421 |
| Sonnet 5 | $0.00011 | $0.00168 |
| Haiku 4.5 | $0.00006 | $0.00084 |
Grade A, and why
docker-up 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage the WealthWise container development environment (Docker or Podman).
Runtime detection
Detect which container runtime is available:
docker info 2>/dev/null | head -1— if it succeeds, usedocker compose- Else
podman info 2>/dev/null | head -1— if it succeeds, usepodman-compose - If neither is available, report the error and stop
Commands by argument
Docker:
| Argument | Action | Command |
|---|---|---|
(none) or dev |
Start dev environment | docker compose up --build -d |
prod |
Start production stack | docker compose -f docker-compose.prod.yml up --build -d |
down |
Stop containers (preserve data) | docker compose down |
down --volumes |
Stop + wipe all volumes (data destroyed) | docker compose down -v |
logs |
Tail all service logs | docker compose logs -f |
logs api or logs web |
Tail one service | docker compose logs -f <service> |
Podman:
| Argument | Action | Command |
|---|---|---|
(none) or dev |
Start dev environment | podman-compose -f podman-compose.yml up --build -d |
prod |
Start production stack | podman-compose -f podman-compose.prod.yml up --build -d |
down |
Stop containers (preserve data) | podman-compose -f podman-compose.yml down |
down --volumes |
Stop + wipe all volumes (data destroyed) | podman-compose -f podman-compose.yml down -v |
logs |
Tail all service logs | podman-compose -f podman-compose.yml logs -f |
logs api or logs web |
Tail one service | podman-compose -f podman-compose.yml logs -f <service> |
Services and ports (dev):
api→ port 4000web→ port 3000mongodb→ port 27017mcp→ port 5100agentic-ai→ port 5200
Pre-flight checks (before starting)
- Docker or Podman daemon is running (see runtime detection)
.envexists inapps/api/:test -f apps/api/.env. Never read it..envexists inapps/web/:test -f apps/web/.env. Never read it.- Port conflicts: check if 4000, 3000, or 27017 are already bound.
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.
- 10d ago First seen · 76 lines · 56 tokens per session scan A 4cd3ac8024ee
docker-up is a skill published in the GitHub repository hoangsonww/WealthWise-Finance-Tracker (24 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 842 once invoked, about $0.0003 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
cis-aws-compute-3.8
Ensure Amazon ECS Fargate services are using the latest Fargate platform version.
aws-cli
CLI-first AWS orchestration skill for Lambda, ECS/Fargate, and S3 workflows rooted in .☁️ runbooks.
ecs
AWS ECS container orchestration for running Docker containers. Use when deploying containerized applications, configuring task definitions, setting up services, managing clusters, or troubleshooting container issues.
eks
AWS EKS Kubernetes management for clusters, node groups, and workloads. Use when creating clusters, configuring IRSA, managing node groups, deploying applications, or integrating with AWS services.
ecspresso
ECS deployment tool - deploy, manage, and troubleshoot ECS services.
ak-cloud-deploy
Deploy an Agent Kernel project to AWS, Azure, or GCP using Terraform modules, or to any Kubernetes cluster (on-prem, baremetal, EKS) using the official Helm chart. Supports serverless and containerized modes for all three clouds. AWS supports execution modes (restsync, restasync, async, stream), queue-based scalable…