discussion-continuity

discussion-continuity is a skill for Claude Code from ahmadulhoq/agentskel. It costs 56 tokens per session (661 once invoked), scanned A, original, MIT.

A workflow guide for saving an interrupted design discussion and bringing it back when work resumes.

In plain words
What is it for?
Use it to record agreed decisions, pending choices, and the exact question that must be answered on return.
Why use it?
It prevents open decisions and unanswered questions from being lost when another task interrupts the discussion.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: installed under .agents/ (shared by several agents).

Part of the agentskel plugin — 53 skills, 3 hooks shipped together

Good fit Use it to record agreed decisions, pending choices, and the exact question that must be answered on return.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ahmadulhoq/agentskel/discussion-continuity
Install

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.

Any agent
npx skills add ahmadulhoq/agentskel --skill discussion-continuity
Clone the repo
git clone --depth 1 https://github.com/ahmadulhoq/agentskel

Made for: Claude Code.

Or install agentskel, the plugin that ships this one along with the rest of its 53 skills, 3 hooks.

Wrote 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.

agentmods badge for discussion-continuity

README.md
[![agentmods](https://agentmods.dev/badge/skills/ahmadulhoq/agentskel/discussion-continuity/github.svg)](https://agentmods.dev/skills/ahmadulhoq/agentskel/discussion-continuity)
Your own site
<a href="https://agentmods.dev/skills/ahmadulhoq/agentskel/discussion-continuity"><img src="https://agentmods.dev/badge/skills/ahmadulhoq/agentskel/discussion-continuity/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.

agentmods 80×15 button for discussion-continuity

Your own site · 80×15
<a href="https://agentmods.dev/skills/ahmadulhoq/agentskel/discussion-continuity"><img src="https://agentmods.dev/badge/skills/ahmadulhoq/agentskel/discussion-continuity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 661 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00056 $0.00661
Opus 5 $0.00028 $0.00331
Sonnet 5 $0.00011 $0.00132
Haiku 4.5 $0.00006 $0.00066

Measured 7d ago against content hash ff4fe7cc932d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

discussion-continuity 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 7d 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.

.agents/skills/discussion-continuity/SKILL.md · 79 lines

How it starts

The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill: Discussion Continuity

Discussions have no formal lifecycle. This skill gives them one — a save point before interruption and a defined retrieval on return.


Operation A — PAUSE (save before switching)

Trigger: Agent has an open unanswered gate question AND the user redirects to a different task or workflow.

Execute as the first action before switching — before any file edits, before any workflow steps.

  1. Write a structured entry to .memory/RESUME.md Session Notes:

    DISCUSSION PAUSED: [topic]
    Agreed: [bullet — one line per agreed decision, or "none yet"]
    Open: [bullet — each pending decision with its options]
    Gate: [exact unanswered question the agent was waiting on]
    
  2. Confirm to the user: "Discussion state saved. Switching to [task]."

  3. Then execute the interrupting task.

Important: The gate field is what prevents treating the return phrase as implementation approval. If the gate is recorded, the agent re-asks it on resume instead of assuming approval.


Operation B — RESUME (resurface on return)

Trigger: Any of:

  • User says "present the discussion," "where were we," "show me the discussion," "back to [topic]," or "resume"
  • task-completion Step 6c detects a DISCUSSION PAUSED: entry in Session Notes

Steps:

  1. Read .memory/RESUME.md Session Notes.
  2. Find any entries prefixed DISCUSSION PAUSED:.
  3. Re-present with full structure — topic, agreed decisions, open decisions with options, and the gate question.
  4. Re-ask the gate question explicitly. Do NOT treat the return phrase as an answer to the gate.
  5. Remove the DISCUSSION PAUSED: entry from Session Notes only after the gate is answered and discussion is resolved or explicitly parked.

Format example

DISCUSSION PAUSED: BACKLOG.md design
Agreed: single flat table with Priority column; ID format BL-NNN; Done capped at 5
Open: (1) Backlog Mode field for Jira? options: column vs config field vs none
      (2) Name — BACKLOG vs TODO?
      (3) Capture convention — how "add to todo" maps to a file
Gate: "Want to proceed with implementation, or adjust the design first?"

Read the full file on GitHub · 79 lines

Changes

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.

  1. 7d ago First seen · 79 lines · 56 tokens per session scan A ff4fe7cc932d

Subscribe to this mod's changes

discussion-continuity is a skill published in the GitHub repository ahmadulhoq/agentskel (13 stars, last pushed 23d ago), licensed MIT. It adds 56 tokens to every session and 661 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-09-02.

Related

Other skills, from other repositories

media-ingest

Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.

garrytan/gbrain · 52 tokens

mem0-oss-to-platform

Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…

mem0ai/mem0 · 273 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

memory

Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.

opensquilla/opensquilla · 44 tokens

ha-data-stores

Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…

shiwenwen/hope-agent · 115 tokens

establishing-project-context

Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.

GanyuanRan/Aegis · 45 tokens