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/joris887/exosuit/deploynpx skills add joris887/exosuit --skill deploygit clone --depth 1 https://github.com/joris887/exosuitWhat 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.00027 | $0.01393 |
| Opus 5 | $0.00014 | $0.00696 |
| Sonnet 5 | $0.00005 | $0.00279 |
| Haiku 4.5 | $0.00003 | $0.00139 |
Grade C, and why
deploy 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 2d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
| Fly.io | `flyctl` | `flyctl version` | `curl -L https://fly.io/install.sh \| sh` | Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| Fly.io | `flyctl` | `flyctl version` | `curl -L https://fly.io/install.sh \| sh` | How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
deploy
Deploy the project to a hosting platform.
Arguments
$1(optional) — platform name override (e.g.,vercel,fly,railway)--dry-run— show what would happen without executing
Step 1: Pre-Deploy Checks
Run the verify-clean-git-state micro-component from .claude/prompts/verify-clean-git-state.md.
Run the discover-commands micro-component from .claude/prompts/discover-commands.md.
Check git state:
- Warn if not on the default branch (but allow if user confirms)
- Warn if there are uncommitted changes
Step 2: Detect Platform
| File / Directory | Platform |
|---|---|
vercel.json or .vercel/ |
Vercel |
netlify.toml or _redirects |
Netlify |
fly.toml |
Fly.io |
railway.json or railway.toml |
Railway |
render.yaml |
Render |
app.yaml (with runtime: or env:) |
Google App Engine |
Procfile + app.json |
Heroku |
amplify.yml or amplify/ |
AWS Amplify |
Dockerfile + (docker-compose.yml or cloud config) |
Container deployment |
- Vercel — best for Next.js, React, static sites. Free tier available.
- Railway — best for full-stack apps with databases. Starts at $5/month.
- Fly.io — best for apps needing global distribution. Free tier for small apps.
- Netlify — best for static sites and Jamstack. Free tier available.
- Render — best for background workers and cron jobs. Free tier available.
- Other — I'll help you set up a Dockerfile for any platform.
Wait for user choice, then guide platform setup (generate config file, install CLI if needed).
</IF>
</ELSE>
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.
- 2d ago First seen · 172 lines · 27 tokens per session scan C a47c11be9978
deploy is a skill published in the GitHub repository joris887/exosuit (4 stars, last pushed 13d ago), licensed MIT. It adds 27 tokens to every session and 1,393 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
issue-triage
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
ship
Build, commit, push & version bump workflow - automates the complete release cycle.
pr-review
Batch review des PRs RTK par ordre de complexité croissante (XS → S → M → L). Pour chaque PR : vérifie l'état (conflits, CLA, reviews), lit le diff complet, analyse le code en contexte, présente un résumé avec lien + taille + recommandation. Attend validation explicite avant tout merge. Poste des commentaires…
rtk-triage
Triage complet RTK : exécute issue-triage + pr-triage en parallèle, puis croise les données pour détecter doubles couvertures, trous sécurité, P0 sans PR, et conflits internes. Sauvegarde dans claudedocs/RTK-YYYY-MM-DD.md. Args: "en"/"fr" pour la langue (défaut: fr), "save" pour forcer la sauvegarde.
code-simplifier
Review RTK Rust code for idiomatic simplification. Detects over-engineering, unnecessary allocations, verbose patterns. Applies Rust idioms without changing behavior.
vercel-optimize
Use for Vercel cost and performance optimization on deployed projects, especially Next.js, SvelteKit, Nuxt, and limited Astro apps. Collect Vercel metrics, usage, project config, and code scan results first; investigate only metric-backed candidates; produce ranked recommendations grounded in verified files and…