mindforge-thread

mindforge-thread is a skill for Claude Code, Codex from sairam0424/MindForge. It costs 12 tokens per session (760 once invoked), scanned A, original, MIT.

A workflow for keeping persistent context threads so work can continue across sessions.

In plain words
What is it for?
Use it to list, resume, create, and update context for longer-running project tasks.
Why use it?
It prevents important background and status from being lost when a session ends.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/sairam0424/mindforge/mindforge-thread
Any agent
npx skills add sairam0424/MindForge --skill mindforge-thread
Clone the repo
git clone --depth 1 https://github.com/sairam0424/MindForge

Made for: Claude Code, Codex.

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 mindforge-thread

README.md
[![agentmods](https://agentmods.dev/badge/skills/sairam0424/mindforge/mindforge-thread.svg)](https://agentmods.dev/skills/sairam0424/mindforge/mindforge-thread)
Your own site
<a href="https://agentmods.dev/skills/sairam0424/mindforge/mindforge-thread"><img src="https://agentmods.dev/badge/skills/sairam0424/mindforge/mindforge-thread.svg" alt="Measured on agentmods" height="20"></a>
Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 760 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00012 $0.00760
Opus 5 $0.00006 $0.00380
Sonnet 5 $0.00002 $0.00152
Haiku 4.5 $0.00001 $0.00076

Measured yesterday against content hash 90300b7ad5fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mindforge-thread 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 yesterday.

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.

.agent/skills/mindforge-thread/SKILL.md · 124 lines

What it actually says

Parse $ARGUMENTS to determine mode:

<mode_list> If no arguments or $ARGUMENTS is empty:

List all threads:

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: /mindforge-thread <description>

</mode_list>

<mode_resume> If $ARGUMENTS matches an existing thread name (file exists):

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

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>

<mode_create> If $ARGUMENTS is a new description (no matching thread file):

Create a new thread:

  1. Generate slug from description:

    SLUG=$(node ".agent/bin/mindforge-tools.cjs" generate-slug "$ARGUMENTS")
    
  2. Create the threads directory if needed:

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

    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:

    node ".agent/bin/mindforge-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: /mindforge-thread {slug}
    

</mode_create>

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. yesterday First seen · 124 lines · 12 tokens per session scan A 90300b7ad5fe

Subscribe to this mod's changes

mindforge-thread is a skill published in the GitHub repository sairam0424/MindForge (0 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 760 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-09-03.

Related

Other skills, from other repositories

cao-memory

Store, recall, and forget durable facts with CAO memory — user preferences, project conventions, decisions, and corrections that should persist across sessions and agents. Use proactively to check memory before asking the user, and to save anything worth remembering. Distinct from any provider-native memory.

awslabs/cli-agent-orchestrator · 59 tokens

cao-learning

Report task outcomes and distill lessons so the team improves across runs — reportoutcome after each unit of work, retrospector handoffs at natural boundaries, and applying injected lessons. Use in workflows that run repeatedly over similar work items. Requires memory.learningenabled; degrade silently when the tools…

awslabs/cli-agent-orchestrator · 63 tokens

cao-supervisor-protocols

Supervisor-side orchestration patterns for assign, handoff, and idle inbox delivery in CAO.

awslabs/cli-agent-orchestrator · 25 tokens

triage

Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked root-cause issue when multiple reports share one underlying invariant failure. Use when a maintainer asks to triage…

arcee-ai/nac · 65 tokens

wrap

End of session. Reflects wins, updates Command Center, moves done tasks, writes to session log and memory.

jdpolasky/ai-chief-of-staff · 25 tokens

project-manager

Manage project-scoped knowledge bases with notes, decisions, and bookmarks. Use when the user wants to create/manage projects, add/view/search notes or decisions for a project, manage bookmarks (add, list, tag to projects), switch project context for conversation, or search across projects. Triggers on phrases like…

OpenCoven/coven · 98 tokens