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 akka/ai-marketplace --skill deploygit clone --depth 1 https://github.com/akka/ai-marketplaceWrote 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/akka/ai-marketplace/deploy)<a href="https://agentmods.dev/skills/akka/ai-marketplace/deploy"><img src="https://agentmods.dev/badge/skills/akka/ai-marketplace/deploy/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/akka/ai-marketplace/deploy"><img src="https://agentmods.dev/badge/skills/akka/ai-marketplace/deploy.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.00035 | $0.02183 |
| Opus 5 | $0.00017 | $0.01092 |
| Sonnet 5 | $0.00007 | $0.00437 |
| Haiku 4.5 | $0.00003 | $0.00218 |
Grade A, and why
deploy 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 9d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
You MUST consider the user input before proceeding (if not empty).
Purpose
This command transitions the service from local development to the
Akka platform. It builds a container image, pushes it to a registry,
deploys it, and configures routing. Only run this when the service works
locally (via /akka:build) and you're ready to ship.
Outline
- Pre-flight checks:
- Run
mvn compileandmvn test— do not deploy if tests fail - Ensure platform context:
- Read
akka://contextresource to check current org/project - If organization is empty:
a. Call
akka_organizations_listto get available orgs b. Present the list to the user and ask which to use c. Remember the chosen org for subsequent tool calls - If project is empty:
a. Call
akka_projects_list(passorganizationparameter if known) b. If projects exist: present list and ask user to pick c. If none: ask if they want to create one viaakka_projects_created. Remember the chosen project for subsequent tool calls - Read
akka://regionsto confirm target region - IMPORTANT: Pass the chosen project as the
projectparameter on every platform tool call. Do NOT callakka config set— that modifies the user's persistent CLI configuration.
- Read
- Check the service name: Read
pom.xmland check the<artifactId>. If it is a scaffold default (e.g.empty-service,my-service,example-service), ask the user what service name they want to deploy as. Use the user's chosen name as theserviceparameter inakka_services_deploy— do NOT rename the artifactId in pom.xml. - Check Docker image store: Docker Desktop may have the containerd
image store enabled, which is incompatible with the Akka container
registry push flow. Check
docker infooutput forcontainerdas the storage driver or image store. If detected, warn the user: "Docker Desktop appears to be using the containerd image store, which is incompatible with the Akka container registry push flow. Please:- Open Docker Desktop → Settings → General
- Uncheck 'Use containerd for pulling and storing images'
- Apply & Restart Docker Desktop
- Run
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.
- 9d ago First seen · 163 lines · 35 tokens per session scan A 863ee9bfc3ad
deploy is a skill published in the GitHub repository akka/ai-marketplace (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 35 tokens to every session and 2,183 once invoked, about $0.0002 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-31.
Other skills, from other repositories
azd-deployment
Deploy containerized frontend + backend applications to Azure Container Apps with remote builds, managed identity, and idempotent infrastructure.
openshell-cli
Guide agents through using the OpenShell CLI (openshell) for sandbox management, gateway registration, provider configuration and refresh, policy iteration, settings, service exposure, BYOC workflows, and inference routing. Covers basic through advanced multi-step workflows. Trigger keywords - openshell, sandbox…
langbot-deploy
Deploy and configure a LangBot instance — Docker / Docker Compose, Kubernetes, the config.yaml model, the Box sandbox runtime, the plugin runtime, and the global API key. Use when installing, deploying, upgrading, or configuring LangBot in production or self-hosted environments. Triggers on "deploy langbot", "langbot…
compute-env-setup
Set up a compute environment on a remote provider so Claude Science jobs can run there. Covers direct SSH/conda hosts, Slurm clusters, container-via-bridge runners, and managed-API providers (Modal, GCP, RunPod). Use when standing up a new provider, porting an env to a different backend, adding a tool that needs its…
atmos-helmfile
Helmfile orchestration: sync/apply/destroy/diff, Kubernetes deployments, varfile generation, EKS integration, source management.
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.