Borrowing it
Nothing to install: this file belongs to chacosoldier/compabob. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/chacosoldier/compabob/main/.claude/agents/crm-relationships.mdgit 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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/chacosoldier/compabob/crm-relationships"><img src="https://agentmods.dev/badge/agents/chacosoldier/compabob/crm-relationships.svg" alt="Reviewed on agentmods" width="80" 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.00752 |
| Opus 5.5 | $0.00028 | $0.00301 |
| Sonnet 5.5 | $0.00014 | $0.00150 |
| 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 1mo 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.
- 1mo ago Changed ff5031537f80
- 1mo ago First seen · 44 lines · 71 tokens per session scan A 052a2386d3af
crm-relationships is an agent published in the GitHub repository chacosoldier/compabob (34 stars, last pushed 5d ago), licensed MIT. It adds 71 tokens to every session and 752 once invoked, about $0.0003 per session on Opus 5.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
task-planner
Implementation planning and task breakdown specialist. Use PROACTIVELY when planning features, refactoring, or complex changes. Creates detailed implementation plans with effort estimates.
product-manager
Product management and value maximization expert. Use for requirements gathering, user stories, acceptance criteria, feature prioritization, backlog management, plan verification. Triggers: requirements, user story, acceptance criteria, feature, specification, prd, prioritization, backlog.
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
sales-closer
PEITHO, fechamento da squad Sales. Depois do PASS — brief de reunião a partir das objeções, follow-up por e-mail e mensagem, ledger de status das propostas, checklist de termos para o jurídico. Só envia com PASS do QA e confirmação; nunca altera preço. Use para apresentação ao cliente e pós-envio.
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).