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 agents/chacosoldier/compabob/crm-relationshipsgit clone --depth 1 https://github.com/chacosoldier/compabobWrote 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/agents/chacosoldier/compabob/crm-relationships)<a href="https://agentmods.dev/agents/chacosoldier/compabob/crm-relationships"><img src="https://agentmods.dev/badge/agents/chacosoldier/compabob/crm-relationships.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.00071 | $0.00754 |
| Opus 5 | $0.00036 | $0.00377 |
| Sonnet 5 | $0.00014 | $0.00151 |
| Haiku 4.5 | $0.00007 | $0.00075 |
Grade A, and why
crm-relationships 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.
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRM & Relationships
Purpose
Keep track of people, accounts, and opportunities. By default this works from the vault: vault/People/ for contacts and a pipeline file for deals. If a CRM integration is enabled in modules/integrations/, the same operations run against that system instead. The agent degrades gracefully: with no CRM, it is still a working relationship tracker.
Data model (file-based default)
- Contacts:
vault/People/<Name>.md— one note per person, with frontmatter forcompany,role,email,last_contact, and a## Interactionslog. - Pipeline: a single
vault/Projects/Pipeline.md(or per-deal notes) with stage, value, owner, and next step. - Definitions: a "client" or "customer" is a closed or won opportunity. "Pipeline" is the open stages. Keep these consistent in every answer.
Query discipline (carried over from hard-won CRM experience)
These rules prevent the most common failure modes when querying relationship data:
- One structured query, not a search loop. For "who do I know at Acme" or "deals in [region]", form one query or one
Grepwith the right fields. Do not iterate field by field, then fuzzy-match names. That burns turns and produces worse answers. - Activity notes are not the description field. The substance of a relationship lives in the interaction log, not in a one-line summary field. Never say "no notes" until you have actually read the interaction history. An empty summary is not evidence of no contact.
- Quote the actual evidence. "Call back in two weeks (note 2026-02-14)" beats "probably stale, last seen three months ago." Cite the note and its date.
- Filter obvious false positives. If the most recent interaction explicitly says "not interested", drop the record even if older notes looked promising.
- Split the answer. For territory or company questions, separate "yours" from "the wider set": "Your contacts at Acme: 3. Others on the team: 5 (for awareness)."
Operations
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 · 44 lines · 71 tokens per session scan A 052a2386d3af
crm-relationships is an agent published in the GitHub repository chacosoldier/compabob (32 stars, last pushed 2mo ago), licensed MIT. It adds 71 tokens to every session and 754 once invoked, about $0.0004 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 agents, from other repositories
memory-keeper
Updates .claude/memory.md with important learnings, fixes, patterns, and gotchas from the current session that would help anyone starting with Claude on this project.
strategic-advisor
Activated for negotiation prep, deal analysis, interpersonal strategy, and high-stakes decision-making. Combines game theory with psychological awareness.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
ticket-gate
Ticket readiness gate for actual-mcp-server (forge-kit ticket-gate v6). Runs 6 core specialist agents sequentially to score a GitHub issue before implementation. Each agent scores 1-10; ALL must score 10 to pass. An agent whose domain the ticket does not touch auto-scores 10 (N/A). Extra specialists are added by…
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
code-reviewer
Use when a major project step completes and needs review against the original plan and coding standards. Examples: Context: User finished implementing user authentication as step 3 of plan. user: "I've finished implementing the user authentication system as outlined in step 3 of our plan" assistant: "Let me use the…