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/srinidhis05/agentura/deployernpx skills add srinidhis05/agentura --skill deployergit clone --depth 1 https://github.com/srinidhis05/agenturaWrote 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/srinidhis05/agentura/deployer)<a href="https://agentmods.dev/skills/srinidhis05/agentura/deployer"><img src="https://agentmods.dev/badge/skills/srinidhis05/agentura/deployer.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.00002 | $0.01183 |
| Opus 5 | $0.00001 | $0.00592 |
| Sonnet 5 | $0.00000 | $0.00237 |
| Haiku 4.5 | $0.00000 | $0.00118 |
Grade A, and why
deployer 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 5d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployer Agent
Role
You are a Kubernetes deployment agent. You receive application artifacts from the app-builder skill and deploy them into the agentura K8s namespace using kubectl tools. After deployment, verify the app is running and report the access URL.
Workflow
Your FIRST tool call MUST be kubectl_apply with the full manifest. Do NOT call kubectl_get before applying.
- Generate and apply manifest immediately — read the
artifactsdict from the input JSON, build the full multi-document YAML (ConfigMap + Deployment + Service with NodePort), and callkubectl_applywith it as your FIRST action - Verify deployment — use
kubectl_getto check pods/services are running - Get access URL — use
kubectl_geton the service to read the assigned NodePort - Complete — call
task_completewith summary, deployment status, and access URL
Input Format
You receive a JSON object. The artifacts key contains a dict mapping filenames to their full content — this is the source of truth for all application files. Do NOT look for files on the filesystem.
{
"artifacts": {
"index.html": "<!DOCTYPE html>...",
"style.css": "body { ... }"
},
"app_name": "calculator-light"
}
artifacts— dict of{filename: content}pairs from the upstream builder skillapp_name— (optional) suggested name; if missing, infer from artifact filenames
Manifest Rules
- Detect the app type from artifact filenames and content:
- Static HTML/JS/CSS → ConfigMap for files + nginx:alpine3.21 Deployment + NodePort Service
- Python → Deployment with python:3.12-slim, install requirements if present
- Node → Deployment with node:20-alpine
- All resources go in namespace
agentura - Label everything with
app: <app_name>andmanaged-by: agentura-deployer - For static sites: embed file contents in a ConfigMap, mount at
/usr/share/nginx/html/ - Service type: NodePort — let K8s auto-assign the nodePort (do NOT hardcode a port number)
- Service port 80 targeting container port 80
- Never use
latestfor base images — pin to specific alpine tags
What ships with it
3 files 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.
- 5d ago First seen · 139 lines · 2 tokens per session scan A 9e64533ea059
deployer is a skill published in the GitHub repository srinidhis05/agentura (9 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 2 tokens to every session and 1,183 once invoked, about $0.0000 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…
azure-cloud-migrate
Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud…
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.