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 skills add jbalbu01/sales-enablement-plugin --skill gtm-memorygit clone --depth 1 https://github.com/jbalbu01/sales-enablement-pluginWrote 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/jbalbu01/sales-enablement-plugin/gtm-memory)<a href="https://agentmods.dev/skills/jbalbu01/sales-enablement-plugin/gtm-memory"><img src="https://agentmods.dev/badge/skills/jbalbu01/sales-enablement-plugin/gtm-memory.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.00124 | $0.03326 |
| Opus 5 | $0.00062 | $0.01663 |
| Sonnet 5 | $0.00025 | $0.00665 |
| Haiku 4.5 | $0.00012 | $0.00333 |
Grade A, and why
gtm-memory 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GTM Memory
The intelligence backbone of the sales enablement system. Every other skill reads from this memory and writes back to it, creating a compounding loop where the system gets smarter with every deal, call, and interaction.
Why This Exists
Traditional enablement creates content and hopes people use it. This system learns from what actually happens in the field — which talk tracks win deals, which discovery questions reveal the most, which objections trip reps up, which competitors keep winning in specific segments — and feeds those insights back into every future interaction.
The result: a plugin that's meaningfully better on day 90 than day 1.
Architecture
┌─────────────────────────────────────────────────────────────────┐
│ GTM MEMORY │
├─────────────────────────────────────────────────────────────────┤
│ KNOWLEDGE STORE (persists across sessions) │
│ 📁 memory/ │
│ ├── product.md — Product details, features, pricing │
│ ├── competitors.md — Competitive landscape + intel log │
│ ├── icp.md — ICP definition + refinements over time │
│ ├── deal-patterns.md — Win/loss patterns, what works │
│ ├── objections.md — Objection library with effectiveness │
│ ├── team.md — Rep profiles, strengths, development │
│ ├── content-registry.md — All enablement assets + freshness │
│ └── changelog.md — All updates with timestamps │
├─────────────────────────────────────────────────────────────────┤
│ WORKING MEMORY (CLAUDE.md — always in context) │
│ • Current priorities and focus areas │
│ • Recent insights not yet integrated │
│ • Active deals requiring attention │
│ • Stale content flags │
│ • Cross-references to memory/ files │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + ~~CRM: Deal outcomes auto-seeding win/loss patterns │
│ + ~~CRM: Contact roles populating buyer committee knowledge │
│ + ~~CRM: Company profiles enriching ICP definitions │
│ + ~~conversation intelligence (Gong): Call patterns & talk tracks│
│ + ~~conversation intelligence (Gong): Objection frequency data │
│ + ~~conversation intelligence (Gong): Discovery question library│
│ + ~~competitive intel (ZoomInfo): Competitor profiles & updates │
│ + ~~competitive intel (ZoomInfo): Tech stack intelligence │
│ + ~~data enrichment (Clay): Company signals & enrichment │
│ + ~~data enrichment (LinkedIn): Stakeholder career movements │
│ + ~~chat: Field feedback and tribal knowledge capture │
│ + ~~calendar/email: Engagement patterns and correspondence │
└─────────────────────────────────────────────────────────────────┘
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.
- 8d ago First seen · 330 lines · 124 tokens per session scan A e8db444cb569
gtm-memory is a skill published in the GitHub repository jbalbu01/sales-enablement-plugin (14 stars, last pushed 6mo ago), licensed MIT. It adds 124 tokens to every session and 3,326 once invoked, about $0.0006 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-30.
Other skills, from other repositories
remember
Stores decisions, patterns, and outcomes in the MCP memory knowledge graph as entities with typed observations and relations. Supports recording architectural decisions, anti-patterns, tool preferences, workflow outcomes, and project conventions that persist across sessions. Use when saving patterns, remembering…
memory
Unified read-side memory operations including knowledge graph search, session context loading, decision timeline viewing, and Mermaid graph visualization. Subcommands: search, load, history, viz, status. Complements /ork:remember (write-side). Use when searching past decisions, loading context, or visualizing the…
neo4j-agent-memory-skill
Authoritative reference for the neo4j-agent-memory Python package — a graph-native memory system for AI agents built on Neo4j — and for the hosted service (NAMS) at memory.neo4jlabs.com. Use this skill whenever the user mentions neo4j-agent-memory, agent memory with Neo4j, context graphs, the POLE+O model…
iwe-restore
A recovery skill that restores an agent’s saved memory and instruction files from an exocortex backup when moving to a new computer or workspace. It shows what it found and asks for confirmation before copying files.
w-reflection
A recording step for storing a scored worldview reflection in a learning database. A worldview reflection is a structured review of assumptions, causes, consequences, and a person's role in a situation.
ke
Knowledge Extraction — captures and routes knowledge at work boundaries. Use when you discover a pattern, make a decision, find a distinction, or complete a sub-task.