deploy-shiny-app

deploy-shiny-app is a skill for Claude Code from pjt222/agent-almanac. It costs 79 tokens per session (1,956 once invoked), scanned C, original, MIT.

A deployment guide for publishing R Shiny applications, which are interactive web apps written in R, to shinyapps.io, Posit Connect, or Docker.

In plain words
What is it for?
Use it to deploy one Shiny app, create a Docker version, configure a custom domain, or set up automated deployments.
Why use it?
It helps move a Shiny app from a developer's computer to a hosted environment with its dependencies and configuration prepared.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the agent-almanac plugin — 122 skills, 77 agents shipped together

Good fit Use it to deploy one Shiny app, create a Docker version, configure a custom domain, or set up automated deployments.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pjt222/agent-almanac/deploy-shiny-app
Install

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.

Any agent
npx skills add pjt222/agent-almanac --skill deploy-shiny-app
Clone the repo
git clone --depth 1 https://github.com/pjt222/agent-almanac

Made for: Claude Code.

Or install agent-almanac, the plugin that ships this one along with the rest of its 122 skills, 77 agents.

Wrote 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.

agentmods badge for deploy-shiny-app

README.md
[![agentmods](https://agentmods.dev/badge/skills/pjt222/agent-almanac/deploy-shiny-app/github.svg)](https://agentmods.dev/skills/pjt222/agent-almanac/deploy-shiny-app)
Your own site
<a href="https://agentmods.dev/skills/pjt222/agent-almanac/deploy-shiny-app"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/deploy-shiny-app/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.

agentmods 80×15 button for deploy-shiny-app

Your own site · 80×15
<a href="https://agentmods.dev/skills/pjt222/agent-almanac/deploy-shiny-app"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/deploy-shiny-app.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 79 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,956 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00079 $0.01956
Opus 5.5 $0.00032 $0.00782
Sonnet 5.5 $0.00016 $0.00391
Haiku 4.5 $0.00008 $0.00196

Measured 1mo ago against content hash 5eaaa4ab9728, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

deploy-shiny-app scanned grade C with 2 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 1mo 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

&& rm -rf /var/lib/apt/lists/*

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

**If fail:** If `appDependencies()` reports missing packages, install them and update `renv.lock`. If the app uses system libraries (e.g., gdal, curl), note them for the Docker path.
i18n/caveman-lite/skills/deploy-shiny-app/SKILL.md · 265 lines

How it starts

The opening of the file, as written. The whole thing — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Deploy Shiny App

Deploy a Shiny application to shinyapps.io, Posit Connect, or a Docker container.

When to Use

  • Publishing a Shiny app for external or internal users
  • Moving from local development to a hosted environment
  • Containerizing a Shiny app for Kubernetes or Docker deployment
  • Setting up automated deployment pipelines

Inputs

  • Required: Path to the Shiny application
  • Required: Deployment target (shinyapps.io, Posit Connect, or Docker)
  • Optional: Account name and token (for shinyapps.io/Connect)
  • Optional: Instance size preference
  • Optional: Custom domain or URL path

Procedure

Step 1: Prepare the Application

Ensure the app is self-contained and deployable:

# Check for missing dependencies
rsconnect::appDependencies("path/to/app")

# For golem apps, ensure DESCRIPTION lists all Imports
devtools::check()

# Verify the app runs cleanly
shiny::runApp("path/to/app")

Verify these files exist:

  • app.R (or ui.R + server.R)
  • renv.lock (recommended for reproducible deployments)
  • .Rprofile does NOT call mcptools::mcp_session() in production

Got: App runs locally without errors and all dependencies are captured.

If fail: If appDependencies() reports missing packages, install them and update renv.lock. If the app uses system libraries (e.g., gdal, curl), note them for the Docker path.

Step 2a: Deploy to shinyapps.io

# One-time account setup
rsconnect::setAccountInfo(
  name = "your-account",
  token = Sys.getenv("SHINYAPPS_TOKEN"),
  secret = Sys.getenv("SHINYAPPS_SECRET")
)

# Deploy
rsconnect::deployApp(
  appDir = "path/to/app",
  appName = "my-app",
  appTitle = "My Application",
  account = "your-account",
  forceUpdate = TRUE
)

Store credentials in .Renviron (never in code):

# .Renviron
SHINYAPPS_TOKEN=your_token_here
SHINYAPPS_SECRET=your_secret_here

Got: App deployed and accessible at https://your-account.shinyapps.io/my-app/.

If fail: If authentication fails, regenerate tokens at shinyapps.io dashboard > Account > Tokens. If package installation fails on the server, check that all packages are available on CRAN — shinyapps.io cannot install from GitHub by default.

Read the full file on GitHub · 265 lines

Changes

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.

  1. 1mo ago First seen · 265 lines · 79 tokens per session scan C 5eaaa4ab9728

Subscribe to this mod's changes

deploy-shiny-app is a skill published in the GitHub repository pjt222/agent-almanac (42 stars, last pushed 5d ago), licensed MIT. It adds 79 tokens to every session and 1,956 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

wrangler

Run or troubleshoot Wrangler CLI commands in projects that have a wrangler.jsonc, wrangler.json, or wrangler.toml file, including local development, Previews, deployment, and resource management. For new projects and projects without a Wrangler configuration file, use the cf CLI instead.

cloudflare/skills · 60 tokens

managing-astro-local-env

Manage local Airflow environment with Astro CLI (Docker and standalone modes). Use when the user wants to start, stop, or restart Airflow, view logs, query the Airflow API, troubleshoot, or fix environment issues. For project setup, see setting-up-astro-project.

astronomer/agents · 63 tokens

aws-cloudformation-ecs

Provides AWS CloudFormation patterns for ECS clusters, task definitions, services, container definitions, auto scaling, blue/green deployments, CodeDeploy integration, ALB integration, service discovery, monitoring, logging, template structure, parameters, outputs, and cross-stack references. Use when creating ECS…

giuseppe-trisciuoglio/developer-kit · 101 tokens

spring-boot-project-creator

Creates and scaffolds a new Spring Boot project (3.x or 4.x) by downloading from Spring Initializr, generating package structure (DDD or Layered architecture), configuring JPA, SpringDoc OpenAPI, and Docker Compose services (PostgreSQL, Redis, MongoDB). Use when creating a new Java Spring Boot project from scratch…

giuseppe-trisciuoglio/developer-kit · 89 tokens

aws-cloudformation-task-ecs-deploy-gh

Provides patterns to deploy ECS tasks and services with GitHub Actions CI/CD. Use when building Docker images, pushing to ECR, updating ECS task definitions, deploying ECS services, integrating with CloudFormation stacks, configuring AWS OIDC authentication for GitHub Actions, and implementing production-ready…

giuseppe-trisciuoglio/developer-kit · 106 tokens

nextjs-deployment

Provides comprehensive patterns for deploying Next.js applications to production. Use when configuring Docker containers, setting up GitHub Actions CI/CD pipelines, managing environment variables, implementing preview deployments, or setting up monitoring and logging for Next.js applications. Covers standalone output…

giuseppe-trisciuoglio/developer-kit · 71 tokens