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 skills add joris887/exosuit --skill continuegit clone --depth 1 https://github.com/joris887/exosuitWrote 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/joris887/exosuit/continue)<a href="https://agentmods.dev/skills/joris887/exosuit/continue"><img src="https://agentmods.dev/badge/skills/joris887/exosuit/continue/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.
<a href="https://agentmods.dev/skills/joris887/exosuit/continue"><img src="https://agentmods.dev/badge/skills/joris887/exosuit/continue.svg" alt="Reviewed on agentmods" width="80" 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.00029 | $0.02503 |
| Opus 5.5 | $0.00012 | $0.01001 |
| Sonnet 5.5 | $0.00006 | $0.00501 |
| Haiku 4.5 | $0.00003 | $0.00250 |
Grade A, and why
continue 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 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.
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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
continue
Skill metrics: Emit a start event to the activity log:
echo "{\"type\":\"skill\",\"event\":\"start\",\"skill\":\"continue\",\"ts\":\"$(date -u +%Y-%m-%dT%H:%M:%SZ)\"}" >> docs/sessions/.activity-log.jsonl
Resume development. Execute this smart continuation workflow:
Current Git State (auto-fetched)
- Branch: !
git branch --show-current - Status: !
git status --short - Open PRs: !
gh pr list --author @me --state open --limit 5 2>/dev/null || echo "No PRs or gh not configured"
0. Project Health Scan
Before session recovery, assess project maturity by checking key artifacts:
| Artifact | Check | If Missing/Incomplete |
|---|---|---|
docs/architecture/ARCHITECTURE.md |
Exists, non-template, Last Verified < 30 days | Suggest /bootstrap if missing; /architecture-check if stale |
docs/reference/GROUND_RULES.md |
Exists and has ≥3 rules | Suggest /bootstrap (A3.5b step) |
docs/reference/CODING_STANDARDS.md |
Exists and non-template | Suggest /bootstrap |
docs/reference/BACKLOG_INDEX.md |
Has ≥1 TODO story | Suggest /ideate |
| Feature branch | git branch --list 'feat/*' 'fix/*' 'sprint-*' |
Suggest /sprint-start |
| Test command | CLAUDE.md Commands has test entry | Suggest configuring tests |
| ADR currency | New ADRs accepted since last session (git log --oneline docs/adr/) |
Surface new decisions that may constrain current work |
| Team workflow | .github/CODEOWNERS exists or >1 contributors |
Surface team tier from docs/reference/TEAM_WORKFLOW.md scaling guide |
Present as a health dashboard before the session state:
### Project Health
- ✅ Architecture documented
- ✅ Ground rules established (5 rules)
- ⚠️ No backlog stories — consider `/ideate`
- ⚠️ Architecture doc stale (Last Verified: 45 days ago) — consider `/architecture-check`
- ❌ Test command not configured
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.
- 1mo ago First seen · 257 lines · 29 tokens per session scan A fdf24b3a9296
continue is a skill published in the GitHub repository joris887/exosuit (8 stars, last pushed 24d ago), licensed MIT. It adds 29 tokens to every session and 2,503 once invoked, about $0.0001 per session on Opus 5.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
rtk-optimizer
Wrap high-verbosity shell commands with RTK to reduce token consumption. Use when running git log, git diff, cargo test, pytest, or other verbose CLI output that wastes context window tokens.
session-save
Save the current session state (decisions, modified files, current status, and next steps) to a handoff file for later resume.
handoff-create
Generate a structured handoff document from the current session. Captures scope, relevant files with line numbers, key discoveries, work completed, current status, next steps, and code snippets. Use before ending a session or handing work to another agent.
handoff-update
Update an existing handoff document with current session progress. Applies section-specific merge rules: append-only for Work Done (never deletes history), replace for Status and Next Steps, merge for Files and Discoveries. Falls back to creating a new handoff if no source file is found.
bulk-reader
Delegate fat file reads to the project's pmread worker. Use when a Read/cat/head/tail/sed of a file over pmread.minlines was blocked, or you must map a large file without ingesting it.
handoff-resume
Load a handoff document and resume work from where a previous session left off. Parses scope, file references, completed work, and next steps, then confirms understanding before proceeding.