graphify

A knowledge-graph tool for B2B sales information. A knowledge graph connects related facts from product catalogs, customer conversations, and market research so they can be searched and analyzed together.

In plain words
What is it for?
Use it to map products and their relationships, connect customer information, find cross-sell opportunities, and examine competitive links.
Why use it?
It helps reveal relationships that are easy to miss when sales information is spread across many files and conversations. The results can support product matching, customer understanding, and competitor analysis.

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/ipythoning/b2b-sdr-agent-template/graphify
Any agent
npx skills add iPythoning/b2b-sdr-agent-template --skill graphify
Clone the repo
git clone --depth 1 https://github.com/iPythoning/b2b-sdr-agent-template

Made for: Claude Code, Codex.

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,371 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.00033 $0.01371
Opus 5 $0.00016 $0.00685
Sonnet 5 $0.00007 $0.00274
Haiku 4.5 $0.00003 $0.00137

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

Security

Grade A, and why

graphify 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.

skills/graphify/SKILL.md · 176 lines

How it starts

The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Graphify — Sales Intelligence Knowledge Graph

Build knowledge graphs from your product catalog, customer conversations, and market research to surface hidden connections, cross-sell opportunities, and competitive insights.

Based on graphify — adapted for B2B SDR context.

Triggers

  • Manual: "Build a knowledge graph of our products"
  • Manual: "Map customer relationships"
  • Manual: "Analyze competitive landscape"
  • Cron (optional): Weekly rebuild after lead-discovery updates

Prerequisites

# Ensure graphify is installed
python3 -c "import graphify" 2>/dev/null || pip install graphifyy -q --break-system-packages 2>&1 | tail -3

Use Cases

1. Product Catalog Graph

Build a graph from product-kb/ to understand product relationships, shared certifications, overlapping target markets, and cross-sell paths.

When to use: Before quotation, during BANT qualification, when customer asks about related products.

python3 -c "
import json
from graphify.extract import collect_files, extract
from graphify.build import build
from graphify.cluster import cluster, score_all
from graphify.analyze import god_nodes, surprising_connections
from pathlib import Path

# Extract from product catalog
files = collect_files(Path('product-kb'))
ast_result = extract(files)

# Build and analyze
G = build([ast_result])
communities, labels = cluster(G)
cohesion = score_all(G, communities)

gods = god_nodes(G, top_n=5)
surprises = surprising_connections(G, communities, top_n=5)

print('=== Core Products (God Nodes) ===')
for g in gods:
    print(f'  {g[\"label\"]} — {g[\"edges\"]} connections')

print('=== Surprising Connections ===')
for s in surprises:
    print(f'  {s[\"source\"]} ↔ {s[\"target\"]} [{s[\"confidence\"]}]')
"

Sales actions from graph insights:

  • God nodes = your anchor products → lead with these in cold outreach
  • Surprising connections = non-obvious cross-sell paths → "customers who buy X often need Y"
  • Communities = product families → bundle pricing opportunities

Read the full file on GitHub · 176 lines

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 · 176 lines · 33 tokens per session scan A 8469441bb71a

Subscribe to this mod's changes

graphify is a skill published in the GitHub repository iPythoning/b2b-sdr-agent-template (166 stars, last pushed 12d ago), licensed MIT. It adds 33 tokens to every session and 1,371 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-30.

Related

Other skills, from other repositories

forward-deployed-selling

Operating doctrine for AI-era enterprise sales. Use when an agent works on accounts, deals, outreach, coaching, or pipeline — any revenue-affecting decision.

vonarmen-wq/forward-deployed-selling · 37 tokens

event-outbound

Create validated, buyer-first email and LinkedIn outreach sequences for B2B conferences and trade shows, from pre-event through post-event. Use when asked to build attendee outreach, cold emails, LinkedIn cadences, side-event or dinner invitations, booth follow-up, or an event-plus-ICP campaign intended to book…

luminik-io/event-outbound-skill · 69 tokens

cold-email-onboarding

First-run interactive setup for the cold-email skill pack. Walks the operator through brand-config.json (ICP, PSP, EVP, tone, infrastructure) and SOUL.md (voice fingerprints, banned phrases, stories you lean on) in 10 minutes. Refuses to let the operator skip — generic output is worse than no output. Loaded…

cmj-hub/claude-cold-email · 91 tokens

cold-email-audit

30-point audit of a B2B outbound program across four dimensions — infrastructure (8 points), targeting (8 points), messaging (8 points), and operations (6 points). Produces a 0-100 score, the top 3 levers, and a 90-day remediation order. Loaded by the main cold-email skill when the user asks to audit or grade their…

cmj-hub/claude-cold-email · 96 tokens

cold-email-deliverability

15-point pre-campaign domain health check across DNS (SPF, DKIM, DMARC, MX, BIMI), reputation (SNDS, Postmaster, blacklists), warm-up status (mailbox age, send volume ramp, reply ratio), and content (spam-trigger lint, link-to-text ratio, image-to-text ratio). Returns a 0-100 deliverability score and a fix-order. Uses…

cmj-hub/claude-cold-email · 134 tokens

cold-email-kickoff

Adaptive router for the cold-email skill pack. Detects the operator's current state (brand-config present? SOUL.md present? infrastructure ready? PSP defined? EVP locked? first campaign run?) and picks the next-best step. Loaded by the main cold-email skill on bare invocation ("/cold-email") or when the operator asks…

cmj-hub/claude-cold-email · 99 tokens