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/quickstartnpx skills add joris887/exosuit --skill quickstartgit 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.00023 | $0.01314 |
| Opus 5 | $0.00012 | $0.00657 |
| Sonnet 5 | $0.00005 | $0.00263 |
| Haiku 4.5 | $0.00002 | $0.00131 |
Grade A, and why
quickstart 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 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.
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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
quickstart
Welcome to the Exosuit framework. This guided tour walks you through your first complete sprint, from planning to shipped PR.
Phase 1: Orientation (2 minutes)
Present the framework's core concept:
### How This Framework Works
The framework adds structure to AI-assisted development:
**Three Layers:**
1. **Enforcement:** hooks that auto-format code, scan for secrets, block dangerous commands (automatic)
2. **Workflow:** skills (slash commands) that guide your development process (you invoke these)
3. **Documentation:** knowledge base that compounds across sessions (generated and updated)
**The Core Loop:**
/sprint-start → /story-cycle (repeat) → /sprint-end
Each `/story-cycle` takes a story through: plan → approve → implement (TDD) → verify → commit.
Phase 2: Check Readiness (1 minute)
Run a quick health check:
# Check if bootstrap has been run
if [ -f "docs/architecture/ARCHITECTURE.md" ] && ! grep -q "<!-- " docs/architecture/ARCHITECTURE.md 2>/dev/null; then
echo "READY: Bootstrap complete"
else
echo "NOT READY: Run /bootstrap first"
fi
Phase 3: Interactive Walkthrough
Present options using AskUserQuestion:
- "Walk me through a sprint" (description: "Interactive guided sprint with explanations at each step (15 min)")
- "Show me all available skills" (description: "Quick reference of every slash command grouped by purpose")
- "Explain the enforcement layer" (description: "See what happens automatically (hooks, rules, quality gates)")
- "I want to start building" (description: "Skip the tour, jump to /sprint-start")
Option A: Guided Sprint Walkthrough
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 · 173 lines · 23 tokens per session scan A 0a89f49dcb2a
quickstart is a skill published in the GitHub repository joris887/exosuit (4 stars, last pushed 13d ago), licensed MIT. It adds 23 tokens to every session and 1,314 once invoked, about $0.0001 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
self-assessment
Interactive skill assessment with personalized learning path generation.
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.