gsd-thread skillA
gsd-thread is agent-read markdown (skill) from coco-research/coco: Use when work spans sessions and does not belong to any specific phase, or when the user wants to create, list or resume a context thread. Keeps lightweight threads under .planning/threads/..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
<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 $ARGUMENTS to determine mode:**
<mode_list>
**If no arguments or $ARGUMENTS 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 $ARGUMENTS 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>
<mode_create>
…Read the whole file at its exact version.
How to install
mdr add coco-research/coco/gsd-thread@git:20260914.e75f220mdr add coco-research/coco/gsd-thread@sha256:fa9ded72a1564ab3Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_7g3o3dzxq7vplojf)
0 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260914.e75f220 latest | 2026-09-14 | e75f220 | 3,197 B | A | view · diff |
| git:20260426.d53cc6c | 2026-04-26 | d53cc6c | 3,063 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3197 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
coco-research/coco · 478 stars · license NOASSERTION · pushed 2026-09-25 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7g3o3dzxq7vplojf GET https://markdownregistry.com/api/v1/resolve?ref=coco-research/coco/gsd-thread GET https://markdownregistry.com/api/v1/blob/fa9ded72a1564ab3953e1df29ca99de22b3eed00c42df94b75b1c308ee3330e3
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.