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.
npx agentmods add skills/andytoizer/gtm-brain-builder/session-relaynpx skills add Andytoizer/gtm-brain-builder --skill session-relaygit clone --depth 1 https://github.com/Andytoizer/gtm-brain-builderWrote 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.
[](https://agentmods.dev/skills/andytoizer/gtm-brain-builder/session-relay)<a href="https://agentmods.dev/skills/andytoizer/gtm-brain-builder/session-relay"><img src="https://agentmods.dev/badge/skills/andytoizer/gtm-brain-builder/session-relay.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00042 | $0.00221 |
| Opus 5 | $0.00021 | $0.00111 |
| Sonnet 5 | $0.00008 | $0.00044 |
| Haiku 4.5 | $0.00004 | $0.00022 |
Grade A, and why
session-relay 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 5d 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.
What it actually says
Session Relay
Use this when a GTM Brain project spans multiple sessions or risks context bloat.
Workflow
- Keep the durable handoff at
projects/{operator}/building-the-brain/README.mdorsession-relay/README.md. - Store transcript links or files under
session-relay/transcripts/. - Do not read JSONL transcripts by default.
- Read transcripts only when the user asks for exact history or the relay README is missing context.
- Before handoff, update the relay README with decisions, completed work, open questions, and the next recommended step.
Handoff Reply Rule
Keep chat handoffs short:
- Repo path.
- Files to read first.
- At most one next step or a compact pickup prompt.
Put detailed state in the relay file, not the chat response.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 27 lines · 42 tokens per session scan A d9f04bd947cd
session-relay is a skill published in the GitHub repository Andytoizer/gtm-brain-builder (8 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 221 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
relevance-coarse-filter
Cheap, high-recall first-pass filter that removes obvious junk from a detector candidate pool before expensive story-origin research and PR judgment. Decides keep, monitoronly, or reject — never ranks, writes angles, verifies dates, or decides whether to pitch.
openkb
Use when the user asks about content in their OpenKB knowledge base — research topics, concepts compiled from their documents, cross-document synthesis — or mentions openkb, an .openkb/ directory, or a wiki/ tree generated by openkb. The user may invoke you from any working directory; the active KB resolves via openkb…
openlore
Query and publish to an OpenLore knowledge base over SSH using ordinary shell commands. Use when a task needs project documentation, runbooks, shared team knowledge, or a place to publish findings.
openlore-housekeeping
Audit and maintain a shared OpenLore knowledge base. Use on a schedule or on request to find stale docs, broken links, unreviewed inbox items, and missing skill coverage, then publish an audit report.
open-cmo
Real-world growth & GTM know-how from 16 tech-company experts. Covers: paid ads (Google/Meta/LinkedIn), out-of-home & ABM, channel selection, PLG→Enterprise, SEO/GEO, programmatic SEO, launches & Product Hunt, pricing & monetization for AI products, ad creative strategy, organic and viral growth, and growth…
content-atomizer
Repurposes single content pieces into multiple formats for maximum distribution while maintaining brand voice. This skill should be used when maximizing ROI from pillar content, filling content calendars efficiently, reaching audiences across multiple platforms, or when creating original content for every channel…