Manage persistent context threads for cross-session work. An agent skill from SpillwaveSolutions/agent-brain.

MITAuto-check passedAgent Workflows

Install Gsd Thread

skills CLI
$ npx skills add SpillwaveSolutions/agent-brain --skill gsd-thread -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install SpillwaveSolutions/agent-brain gsd-thread --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/gsd-thread .claude/skills/gsd-thread && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
gsd-thread
GitHub stars
120
Used in
3 other repos
Token cost
~1.2k tokens
SKILL.md length
440 words
Files
1
Skills in repo
55
Repo updated
First seen
Licence
MIT

At a glance

Manage persistent context threads for cross-session work. An agent skill from SpillwaveSolutions/agent-brain.

  • Works in 6 steps: Generate slug from description → Create the threads directory if needed → Write the thread file → …
  • Tasks that involve Session handoff
  • SKILL.md covers A. Skill Invocation, B. AskUserQuestion →… and C. Task() → spawn_agent Mapping
  • Calls node

What it does

Gsd Thread is an agent skill from SpillwaveSolutions/agent-brain. Manage persistent context threads for cross-session work

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Session handoff. The repository describes itself as: Local-first RAG memory for AI agents: hybrid + GraphRAG search, MCP server with OAuth 2.1, plugin for Claude Code / OpenCode / Codex. The licence is MIT.

When your agent uses it

  • Tasks that involve Session handoff

Example prompts

  • “/gsd-thread”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Generate slug from description
  2. Create the threads directory if needed
  3. Write the thread file
  4. If there's relevant context in the current conversation (code snippets,
  5. Commit
  6. Report

What it can do on your machine

Read from SKILL.md and the folder at commit 8339623. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Gsd Thread loads about 1.2k tokens when it runs. Until then it costs about 17 tokens; SKILL.md has 440 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~17
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from SpillwaveSolutions/agent-brain at commit 8339623, republished under its MIT licence (© SpillwaveSolutions). 440 words, ~1,229 tokens.

Download SKILL.mdSave it as .claude/skills/gsd-thread/SKILL.md (or your agent's skills folder).
name
gsd-thread
description
Manage persistent context threads for cross-session work
metadata.short-description
Manage persistent context threads for cross-session work

<codex_skill_adapter>

A. Skill Invocation

  • This skill is invoked by mentioning $gsd-thread.
  • Treat all user text after $gsd-thread as {{GSD_ARGS}}.
  • If no arguments are present, treat {{GSD_ARGS}} as empty.

B. AskUserQuestion → request_user_input Mapping

GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:

Parameter mapping:

  • header → header
  • question → question
  • Options formatted as "Label" — description → {label: "Label", description: "description"}
  • Generate id from header: lowercase, replace spaces with underscores

Batched calls:

  • AskUserQuestion([q1, q2]) → single request_user_input with multiple entries in questions[]

Multi-select workaround:

  • Codex has no multiSelect. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.

Execute mode fallback:

  • When request_user_input is rejected (Execute mode), present a plain-text numbered list and pick a reasonable default.

C. Task() → spawn_agent Mapping

GSD workflows use Task(...) (Claude Code syntax). Translate to Codex collaboration tools:

Direct mapping:

  • Task(subagent_type="X", prompt="Y") → spawn_agent(agent_type="X", message="Y")
  • Task(model="...") → omit (Codex uses per-role config, not inline model selection)
  • fork_context: false by default — GSD agents load their own context via <files_to_read> blocks

Parallel fan-out:

  • Spawn multiple agents → collect agent IDs → wait(ids) for all to complete

Result parsing:

  • Look for structured markers in agent output: CHECKPOINT, PLAN COMPLETE, SUMMARY, etc.
  • close_agent(id) after collecting results from each agent </codex_skill_adapter>
<objective>
Create, list, or resume persistent context threads. Threads are lightweight
cross-session knowledge stores for work that spans multiple sessions but
doesn't belong to any specific phase.
</objective>
<process>

Parse {{GSD_ARGS}} to determine mode:

<mode_list> If no arguments or {{GSD_ARGS}} is empty:

List all threads:

bash
ls .planning/threads/*.md 2>/dev/null

For each thread, read the first few lines to show title and status:

## Active Threads

| Thread | Status | Last Updated |
|--------|--------|-------------|
| fix-deploy-key-auth | OPEN | 2026-03-15 |
| pasta-tcp-timeout | RESOLVED | 2026-03-12 |
| perf-investigation | IN PROGRESS | 2026-03-17 |

If no threads exist, show:

No threads found. Create one with: $gsd-thread <description>

</mode_list>

<mode_resume> If {{GSD_ARGS}} matches an existing thread name (file exists):

Resume the thread — load its context into the current session:

bash
cat ".planning/threads/${THREAD_NAME}.md"

Display the thread content and ask what the user wants to work on next. Update the thread's status to IN PROGRESS if it was OPEN. </mode_resume>

Show full SKILL.md (196 more words)Show less

<mode_create> If {{GSD_ARGS}} is a new description (no matching thread file):

Create a new thread:

  1. Generate slug from description:

    bash
    SLUG=$(node "/Users/richardhightower/clients/spillwave/src/agent-brain/.codex/get-shit-done/bin/gsd-tools.cjs" generate-slug "{{GSD_ARGS}}")
  2. Create the threads directory if needed:

    bash
    mkdir -p .planning/threads
  3. Write the thread file:

    bash
    cat > ".planning/threads/${SLUG}.md" << 'EOF'
    # Thread: {description}
    
    ## Status: OPEN
    
    ## Goal
    
    {description}
    
    ## Context
    
    *Created from conversation on {today's date}.*
    
    ## References
    
    - *(add links, file paths, or issue numbers)*
    
    ## Next Steps
    
    - *(what the next session should do first)*
    EOF
  4. If there's relevant context in the current conversation (code snippets, error messages, investigation results), extract and add it to the Context section.

  5. Commit:

    bash
    node "/Users/richardhightower/clients/spillwave/src/agent-brain/.codex/get-shit-done/bin/gsd-tools.cjs" commit "docs: create thread — ${ARGUMENTS}" --files ".planning/threads/${SLUG}.md"
  6. Report:

    ## 🧵 Thread Created
    
    Thread: {slug}
    File: .planning/threads/{slug}.md
    
    Resume anytime with: $gsd-thread {slug}

</mode_create>

</process>
<notes>
- Threads are NOT phase-scoped — they exist independently of the roadmap
- Lighter weight than $gsd-pause-work — no phase state, no plan context
- The value is in Context and Next Steps — a cold-start session can pick up immediately
- Threads can be promoted to phases or backlog items when they mature:
  $gsd-add-phase or $gsd-add-backlog with context from the thread
- Thread files live in .planning/threads/ — no collision with phases or other GSD structures
</notes>

© SpillwaveSolutions, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .codex/skills/gsd-thread of SpillwaveSolutions/agent-brain.

Open the folder on GitHubat commit 8339623

Used in 3 other repositories

We found 14 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in SpillwaveSolutions/agent-brain, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Gsd Thread next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Gsd Thread compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Gsd Thread this skillSpillwaveSolutions/agent-brain1203 repos~1.2kAutomated safety check: PassMIT
Orca CLIstablyai/orca87k2 repos~593Automated safety check: PassMIT
Beads Task Memorygastownhall/beads28k—~1.2kAutomated safety check: PassMIT
Session History Searchslopus/happy24k—~3.1kAutomated safety check: PassMIT
Paseo Agent Handoffgetpaseo/paseo20k1 repos~606Automated safety check: PassCustom licence
Memori Long-Term MemoryMemoriLabs/Memori17k—~2kAutomated safety check: NotesCustom licence

Similar skills

  • Orca CLI

    stablyai/orca

    Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…

    87k GitHub starsUsed in 2 repos~593 tokens
    Agent WorkflowsAuto-check passed
  • Beads Task Memory

    gastownhall/beads

    Tracks multi-session work with dependencies in the bd issue tracker so the agent can find ready tasks and recover its context after conversation compaction.

    28k GitHub stars~1.2k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Searches past Claude Code, Codex and Cursor sessions and summarizes what was worked on, tried or decided, using extraction scripts instead of reading raw logs.

    24k GitHub stars~3.1k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Paseo Agent Handoff

    getpaseo/paseo

    Hands off the current task, including context, decisions and failed attempts, to a fresh agent through Paseo by writing a self-contained briefing prompt and launching that agent.

    20k GitHub starsUsed in 1 repo~606 tokens
    Agent WorkflowsAuto-check passed
  • Memori Long-Term Memory

    MemoriLabs/Memori

    Connects Claude Code to Memori Cloud for long-term memory, recalling stored context before substantive replies and saving new context afterward.

    17k GitHub stars~2k tokensUpdated 5 days ago
    Agent WorkflowsAuto-check: notes
  • Beads

    liwp/again

    A skill your agent uses when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory.

    118 GitHub starsUsed in 6 repos~537 tokens
    Agent WorkflowsAuto-check passed

More from SpillwaveSolutions/agent-brain

All 55 skills in this repo
  • Gsd Complete Milestone

    SpillwaveSolutions/agent-brain

    Archive completed milestone and prepare for next version. An agent skill from SpillwaveSolutions/agent-brain.

    120 GitHub starsUsed in 4 repos~1.6k tokens
    Auto-check passed
  • Mastering Python Skill

    SpillwaveSolutions/agent-brain

    Modern Python coaching covering language foundations through advanced production patterns.

    120 GitHub stars~1.4k tokensUpdated 18 days ago
    Auto-check: notes
  • Gsd Debug

    SpillwaveSolutions/agent-brain

    Systematic debugging with persistent state across context resets

    120 GitHub starsUsed in 4 repos~1.5k tokens
    Auto-check passed
  • Gsd Review Backlog

    SpillwaveSolutions/agent-brain

    Review and promote backlog items to active milestone. An agent skill from SpillwaveSolutions/agent-brain.

    120 GitHub starsUsed in 3 repos~961 tokens
    Auto-check passed
  • Configuring Agent Brain

    SpillwaveSolutions/agent-brain

    Installation and configuration skill for Agent Brain document search system.

    120 GitHub stars~7k tokensUpdated 18 days ago
    Auto-check: notes
  • Gsd Plant Seed

    SpillwaveSolutions/agent-brain

    Capture a forward-looking idea with trigger conditions — surfaces automatically at the right milestone

    120 GitHub starsUsed in 2 repos~691 tokens
    Auto-check passed

Categories

Questions about Gsd Thread

What does Gsd Thread do?

Manage persistent context threads for cross-session work. An agent skill from SpillwaveSolutions/agent-brain. Gsd Thread is an agent skill from SpillwaveSolutions/agent-brain.

When should I use Gsd Thread?

Gsd Thread fits situations like: tasks that involve Session handoff.

How do I install Gsd Thread in Claude Code?

Run `npx skills add SpillwaveSolutions/agent-brain --skill gsd-thread -a claude-code`. Or copy the skill folder (.codex/skills/gsd-thread in SpillwaveSolutions/agent-brain) into .claude/skills/gsd-thread in your project. Claude Code loads it when a task matches its description.

How do I install Gsd Thread in Codex?

Run `npx skills add SpillwaveSolutions/agent-brain --skill gsd-thread -a codex`. Or copy the skill folder (.codex/skills/gsd-thread in SpillwaveSolutions/agent-brain) into .agents/skills/gsd-thread in your project. Codex loads it when a task matches its description.

Can I use Gsd Thread in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add SpillwaveSolutions/agent-brain --skill gsd-thread -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gsd-thread, .gemini/skills/gsd-thread, .github/skills/gsd-thread and .opencode/skills/gsd-thread in your project.

What does Gsd Thread need to run?

Going by SKILL.md and its folder, Gsd Thread needs the command-line tools its instructions call (node).

Does Gsd Thread access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Gsd Thread safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Gsd Thread use?

Gsd Thread is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gsd Thread use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Gsd Thread?

Skills that share tags, products or a category with Gsd Thread: Orca CLI (stablyai/orca, 87k stars), Beads Task Memory (gastownhall/beads, 28k stars), Session History Search (slopus/happy, 24k stars) and Paseo Agent Handoff (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gsd Thread?

SpillwaveSolutions (a GitHub organization) maintains it in SpillwaveSolutions/agent-brain, which has 120 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on September 19, 2026.

Source: SpillwaveSolutions/agent-brain on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.