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/gotempsh/temps/deploy-to-tempsnpx skills add gotempsh/temps --skill deploy-to-tempsgit clone --depth 1 https://github.com/gotempsh/tempsWrote 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/gotempsh/temps/deploy-to-temps)<a href="https://agentmods.dev/skills/gotempsh/temps/deploy-to-temps"><img src="https://agentmods.dev/badge/skills/gotempsh/temps/deploy-to-temps.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 | $0.00141 | $0.01444 |
| Opus 5 | $0.00071 | $0.00722 |
| Sonnet 5 | $0.00028 | $0.00289 |
| Haiku 4.5 | $0.00014 | $0.00144 |
Grade A, and why
deploy-to-temps 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST https://your-temps.com/api/projects/123/deploy \ How it starts
The opening of the file, as written. The whole thing — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy to Temps
Deploy applications to Temps with automatic framework detection and optimized builds.
Supported Frameworks
| Framework | Detection | Build Command |
|---|---|---|
| Next.js | next.config.* |
next build |
| Vite | vite.config.* |
vite build |
| Create React App | react-scripts in package.json |
react-scripts build |
| Remix | remix.config.* |
remix build |
| Express/Node.js | express in dependencies |
npm run build (if exists) |
| NestJS | @nestjs/core in dependencies |
nest build |
| Python/Flask | requirements.txt + app.py |
- |
| Python/Django | manage.py |
python manage.py collectstatic |
| Go | go.mod |
go build |
| Rust | Cargo.toml |
cargo build --release |
Quick Deploy
Via Git Integration
- Connect your Git provider in Temps dashboard
- Select repository and branch
- Temps auto-detects framework and deploys
Via CLI
# Install Temps CLI
npm install -g @temps-sdk/cli
# Login
temps login
# Deploy current directory
temps deploy
# Deploy with specific settings
temps deploy --project my-app --branch main
Dockerfile Generation
Temps auto-generates optimized Dockerfiles. For custom needs:
Next.js (Standalone)
FROM node:20-alpine AS base
FROM base AS deps
WORKDIR /app
COPY package*.json ./
RUN npm ci
FROM base AS builder
WORKDIR /app
COPY --from=deps /app/node_modules ./node_modules
COPY . .
RUN npm run build
FROM base AS runner
WORKDIR /app
ENV NODE_ENV=production
RUN addgroup --system --gid 1001 nodejs
RUN adduser --system --uid 1001 nextjs
COPY --from=builder /app/public ./public
COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static
USER nextjs
EXPOSE 3000
ENV PORT=3000
CMD ["node", "server.js"]
Node.js (Express/Fastify)
FROM node:20-alpine
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY . .
ENV NODE_ENV=production
USER node
EXPOSE 3000
CMD ["node", "dist/index.js"]
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 · 255 lines · 141 tokens per session scan A a120b4aa244e
deploy-to-temps is a skill published in the GitHub repository gotempsh/temps (712 stars, last pushed yesterday), licensed Apache-2.0. It adds 141 tokens to every session and 1,444 once invoked, about $0.0007 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
scanning-docker-images-with-trivy
Trivy is a comprehensive open-source vulnerability scanner by Aqua Security that detects vulnerabilities in OS packages, language-specific dependencies, misconfigurations, secrets, and license violati.
performing-container-security-scanning-with-trivy
Scan container images, filesystems, and Kubernetes manifests for vulnerabilities, misconfigurations, exposed secrets, and license compliance issues using Aqua Security Trivy with SBOM generation and CI/CD integration.
devops-deployment
Use when setting up CI/CD pipelines, containerizing applications, deploying to Kubernetes, or writing infrastructure as code. DevOps & Deployment covers GitHub Actions, Docker, Helm, and Terraform patterns.
add-ci-area
Add a new project area to CI workflows.
ci-status
Check the CI pipeline status for the current branch after pushing changes. Reports pass/fail with failure details. Use this after every push to confirm your changes are truly done — CI must be green. TRIGGER when: after git push, after committing changes, when asked to check CI, or when verifying that work is complete.
deployment
Use when taking an app from source to live: choosing the deploy target from requirements (Hetzner+Coolify vs Vercel vs a third), then wiring container → CI → registry → host with build secrets, healthchecks and rollback. NOT one platform's mechanics (that is coolify, vercel, railway, render), NOT the Dockerfile alone…