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/konamgil/mandu/mandu-deploynpx skills add konamgil/mandu --skill mandu-deploygit clone --depth 1 https://github.com/konamgil/manduWrote 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/konamgil/mandu/mandu-deploy)<a href="https://agentmods.dev/skills/konamgil/mandu/mandu-deploy"><img src="https://agentmods.dev/badge/skills/konamgil/mandu/mandu-deploy.svg" alt="Measured on agentmods" 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.00020 | $0.01072 |
| Opus 5 | $0.00010 | $0.00536 |
| Sonnet 5 | $0.00004 | $0.00214 |
| Haiku 4.5 | $0.00002 | $0.00107 |
Grade A, and why
mandu-deploy 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 6d 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.
test: ["CMD", "curl", "-f", "http://localhost:3333/api/health"] How it starts
The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mandu Deploy
프로덕션 배포 파이프라인 가이드. Build -> Test -> Deploy 체크리스트와 Docker/CI-CD/nginx 설정을 다룹니다.
Build -> Test -> Deploy Checklist
1. Pre-Deploy Checks
# Architecture validation
bunx mandu guard arch --ci
# TypeScript check
bunx tsc --noEmit
# Run tests
bun test
# Production build
bun run build
2. Dockerfile
FROM oven/bun:1.3.14-alpine AS base
WORKDIR /app
# Install dependencies
FROM base AS deps
COPY package.json bun.lock* ./
RUN bun install --frozen-lockfile --production
# Build
FROM base AS build
COPY package.json bun.lock* ./
RUN bun install --frozen-lockfile
COPY . .
RUN bun run build
# Production
FROM base AS production
COPY --from=deps /app/node_modules ./node_modules
COPY --from=build /app/.mandu ./.mandu
COPY --from=build /app/app ./app
COPY --from=build /app/src ./src
COPY --from=build /app/spec ./spec
COPY --from=build /app/package.json ./
ENV NODE_ENV=production
ENV PORT=3333
EXPOSE 3333
CMD ["bun", "run", "start"]
3. docker-compose.yml
version: "3.8"
services:
app:
build: .
ports:
- "3333:3333"
environment:
- NODE_ENV=production
- DATABASE_URL=${DATABASE_URL}
restart: unless-stopped
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:3333/api/health"]
interval: 30s
timeout: 10s
retries: 3
4. GitHub Actions CI/CD
# .github/workflows/deploy.yml
name: Deploy
on:
push:
branches: [main]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: oven-sh/setup-bun@v2
with:
bun-version: latest
- run: bun install --frozen-lockfile
- run: bunx mandu guard arch --ci
- run: bun test
- run: bun run build
- name: Deploy
run: |
# docker build & push, or platform-specific deploy
docker build -t myapp:${{ github.sha }} .
docker push myapp:${{ github.sha }}
5. nginx Reverse Proxy
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.
- 6d ago First seen · 180 lines · 20 tokens per session scan A fb64b8200762
mandu-deploy is a skill published in the GitHub repository konamgil/mandu (46 stars, last pushed 10d ago), licensed MPL-2.0. It adds 20 tokens to every session and 1,072 once invoked, about $0.0001 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-30.
Other skills, from other repositories
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
ag-preparar-ambiente
Gera e mantém infraestrutura de desenvolvimento e CI/CD: Dockerfile, docker-compose, pipeline, env vars. Dev novo roda em 10 min.
ci-cd-devops-architect
Expert guide for continuous integration, deployment pipelines, Docker, Kubernetes, and Infrastructure as Code (IaC) / Panduan ahli untuk CI/CD dan infrastruktur.
devops
Deployment and infrastructure operations. Use when writing or debugging a Dockerfile, docker build/run, docker compose; running terraform plan/apply/destroy or editing .tf files and modules; using kubectl, debugging pods (CrashLoopBackOff, ImagePullBackOff, OOMKilled), applying manifests, or writing Helm charts…
ci-self-heal
针对 CI 失败日志输出结构化诊断与修复建议. 识别失败分类(test/lint/build/type/dependency/config/flaky/timeout) / 根因假设 / 可执行 fix, 引用具体 file:line. 专为 PR-to-Prod 流程的 CI 卡点兜底设计.
devops
Deploy and manage infrastructure with Docker, Kubernetes, CI/CD pipelines, and cloud services. Use when containerizing, deploying, or managing production infrastructure.