agami-deploy SKILL.md skillB
agami-deploy from agamiai/agami-core is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add agamiai/agami-core/agami-deploy@git:20261011.c18f7cdPins git:20261011.c18f7cd in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- agamiai/agami-core
- Path
plugins/agami/skills/agami-deploy/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261011.c18f7cd, committed Oct 11, 2026
- First version recorded
- Jul 4, 2026
- Size
- 11,641 bytes
- Repository stars
- 29
- License
- a license file GitHub does not identify
EARLY ACCESS (in testing) — usable today, but newer than the local single-player path; feedback welcome via a GitHub issue. Prepares a ready-to-run, self-hosted agami deploy bundle ON THE USER'S MACHINE so a team can stand up a shareable MCP server their Claude connects to. Conversationally gathers the hard-floor inputs (hostname, admin identity), auto-detects the local model, writes docker-compose.yml + Caddyfile + a filled agami.env (referencing the PUBLISHED image ghcr.io/agamiai/agami-core…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# agami deploy — prepare a self-host bundle the user ships to their own host You are preparing a **deploy bundle** on the user's machine so they can stand up the multi-user agami server (the HTTP MCP server with OAuth + admin) that their team's Claude connects to. The bundle pulls the **published image** (`ghcr.io/agamiai/agami-core`) — there is **no repo to clone and nothing to build**. You gather a few inputs, write the bundle locally, and hand off the cloud steps you can't do. The local mirror of this (single-player, no network, no auth) is `agami-serve` — if the user only wants agami in their own Claude Desktop, point them there instead. ## HARD RULES (load-bearing — a deploy handles secrets) 1. **Never ask for the admin password (or any secret) in chat — not even temporarily.** The password is typed by the **user** directly into the `agami.env` file (Phase 2 hand-off), exactly like `agami-connect` does for DB credentials. You never see it. 2. **Never put a secret on a Bash command line.** `prepare_deploy.py` takes only non-secret values; `deploy_preflight` generates the signing secret *into the file*. Hosts render Bash calls in chat. …
Read the whole file at its exact version.
How to install
mdr add agamiai/agami-core/agami-deploy@sha256:7cf46e85e4db8fb7The line at the top of this page pins the label git:20261011.c18f7cd, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_jcg5ihv4uj2ap5ph)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jul 4, 2026 and Oct 11, 2026, about one every 20 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261011.c18f7cd latest | 2026-10-11 | c18f7cd | 11,641 B | B | view · diff |
| git:20260725.62fb100 | 2026-07-25 | 62fb100 | 11,641 B | B | view · diff |
| git:20260713.f77a88e | 2026-07-13 | f77a88e | 11,627 B | B | view · diff |
| git:20260706.3a8713f | 2026-07-06 | 3a8713f | 11,501 B | B | view · diff |
| git:20260704.eb38888 | 2026-07-04 | eb38888 | 11,255 B | B | view · diff |
| git:20260704.3327883 | 2026-07-04 | 3327883 | 9,199 B | B | view |
Audit of the latest version
- fail: No curl or wget piped into a shell (matched: curl -fsSL https://get.docker.com | sudo sh)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11641 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
agamiai/agami-core · 29 stars · license a license file GitHub does not identify · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jcg5ihv4uj2ap5ph GET https://markdownregistry.com/api/v1/resolve?ref=agamiai/agami-core/agami-deploy GET https://markdownregistry.com/api/v1/blob/7cf46e85e4db8fb7f1ec65445e8ef47e2ce7e59ef00851fba6ae577b1ece4f69
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.