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 dhruv-anand-aintech/continue-later-skill --skill continue-latergit clone --depth 1 https://github.com/dhruv-anand-aintech/continue-later-skillWrote 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/dhruv-anand-aintech/continue-later-skill/continue-later)<a href="https://agentmods.dev/skills/dhruv-anand-aintech/continue-later-skill/continue-later"><img src="https://agentmods.dev/badge/skills/dhruv-anand-aintech/continue-later-skill/continue-later/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/dhruv-anand-aintech/continue-later-skill/continue-later"><img src="https://agentmods.dev/badge/skills/dhruv-anand-aintech/continue-later-skill/continue-later.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.00055 | $0.01049 |
| Opus 5 | $0.00028 | $0.00524 |
| Sonnet 5 | $0.00011 | $0.00210 |
| Haiku 4.5 | $0.00006 | $0.00105 |
Grade A, and why
continue-later 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 9d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Continue Later
Generate and manage project continuation documentation for seamless handoffs, team transitions, and knowledge preservation across coding sessions.
Overview
When the user asks to hand off work, save state, or create a continuation, generate a comprehensive continuation.md following this structure.
Use this skill when the user says:
- "Hand this off" / "Continue later" / "Save project state"
- "Create a continuation for the team"
- "Document where we left off"
- "I'm done for the day, create handoff docs"
For summarizing handoff files, use resume-from-earlier (/resume-from-earlier) or resume-continuation (natural phrasing); both read continuation.md and/or continuation-fast.md—prefer structured continuation.md when both exist. For a raw git-focused dump, use continue-later-fast (writes continuation-fast.md).
Continuation.md Structure
When generating a continuation, create a file with these sections. Be specific—use actual project context, not placeholders.
# Continuation: [Project Name]
**Date:** YYYY-MM-DD
**Working directory:** [absolute path]
---
## What This Project Is
[2-3 sentences. What does it do, for whom, and why it matters.]
## Tech Stack
[Bullet list: language, frameworks, databases, key libraries]
## How to Build & Run
[Exact commands. Nothing assumed.]
## Key Files
| File | Purpose |
|------|---------|
| path/to/file | What it does |
## What Was Just Done (Most Recent Session)
[Chronological summary of changes. Be specific: what was changed, why, what bug it fixed. Include the actual fix—not just "fixed bug X".]
## Current State
**Working:**
- [List what demonstrably works]
**Broken / Known Issues:**
- [List known bugs with root cause if known]
**In Progress:**
- [Anything half-done or partially implemented]
## Pending Tasks
[Ordered list of what the user still wants done, in priority order. Copy verbatim from the user's most recent requests if possible.]
## Key Technical Decisions
[Decisions made during the session that a new agent must not undo or re-litigate. Include the *why*.]
## Gotchas & Traps
[Anything that caused problems, wasted time, or was non-obvious. Future agent must know these. Format:]
**Title**
Description of what went wrong.
**Solution:** How to fix it.
**Lesson:** What we learned.
## How to Deploy
[Exact commands to build, package, and deploy.]
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.
- 9d ago First seen · 114 lines · 55 tokens per session scan A 12cc8271f5aa
continue-later is a skill published in the GitHub repository dhruv-anand-aintech/continue-later-skill (3 stars, last pushed 3mo ago), licensed MIT. It adds 55 tokens to every session and 1,049 once invoked, about $0.0003 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
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
contact-cache
Track all identified/contacted people across strategies. CSV-backed contact database with dedup by LinkedIn URL or email. Prevents duplicate outreach when running strategies on a recurring cadence.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.