search-shared-sessions skillA
search-shared-sessions is agent-read markdown (skill) from agentworkforce/relay: Search an Agent Relay workspace's shared coding-agent sessions for prior work, decisions, fixes, or the context behind a task or pull request. Use when team history could answer the user's question or prevent repeating an investigation..
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
# Search shared sessions Use the shared-session MCP tools with the user's selected Agent Relay Cloud workspace. Tool discovery supplies the current arguments and supported filters. 1. Call `search_shared_sessions` with concrete terms from the question: error text, component names, task identifiers, or distinctive implementation terms. Narrow by supported project, source, or time filters when the user provides them. Try a few alternate terms if the first query misses. 2. Use `get_shared_session` to inspect a matching session and `get_shared_session_context` to read the relevant conversation. Preserve returned session identifiers and source values when following a match. Follow pagination when more context is needed; report truncation or incomplete coverage when it affects the answer. 3. Explain what the history supports and cite the returned replay links. Distinguish a past plan from completed work and from the current repository state. Verify current code when the question depends on what is implemented now. …
Read the whole file at its exact version.
How to install
mdr add agentworkforce/relay/search-shared-sessions@git:20260921.3070582mdr add agentworkforce/relay/search-shared-sessions@sha256:eb195e48b556f3d5Pin 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_kkiequd7h5ea6zzz)
1 badge views in 30 days
Versions
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 (2323 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
agentworkforce/relay · 849 stars · license Apache-2.0 · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kkiequd7h5ea6zzz GET https://markdownregistry.com/api/v1/resolve?ref=agentworkforce/relay/search-shared-sessions GET https://markdownregistry.com/api/v1/blob/eb195e48b556f3d532092530e4f652dff599dcadd4f0244d77d572de56c3f5e9
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.