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 anh-chu/llm-wiki-pm --skill llm-wiki-crmgit clone --depth 1 https://github.com/anh-chu/llm-wiki-pmWrote 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/anh-chu/llm-wiki-pm/llm-wiki-crm)<a href="https://agentmods.dev/skills/anh-chu/llm-wiki-pm/llm-wiki-crm"><img src="https://agentmods.dev/badge/skills/anh-chu/llm-wiki-pm/llm-wiki-crm/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/skills/anh-chu/llm-wiki-pm/llm-wiki-crm"><img src="https://agentmods.dev/badge/skills/anh-chu/llm-wiki-pm/llm-wiki-crm.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.00058 | $0.02065 |
| Opus 5 | $0.00029 | $0.01033 |
| Sonnet 5 | $0.00012 | $0.00413 |
| Haiku 4.5 | $0.00006 | $0.00206 |
Grade A, and why
llm-wiki-crm 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 12d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LLM Wiki CRM
CRM layer on top of the PM wiki. Tracks relationship health, account status, feature asks, and auto-enrichment for people and company entities. Complements Salesforce — this layer captures PM-specific context that CRMs don't: product feedback, feature asks, communication history, strategic relationship signals.
When This Skill Activates
- "relationship health", "who haven't I talked to", "dormant accounts", "check relationships"
- "enrich [person/company]", "auto-enrich [person/company]", "fill in [person/company] details" (This skill enriches relationship/CRM context — tier, touchpoint, feature asks. For factual/web enrichment of a stub page, use llm-wiki-research's Auto-Research.)
- "account health", "strategic accounts", "how are my accounts"
- "what do customers want", "feature asks", "what are accounts asking for", "customer asks"
- "log touchpoint with [person/company]", "update [entity] relationship", "set [entity] to strategic"
- "CRM", "key accounts", "contact cadence", "overdue contacts"
New CRM Frontmatter Fields
These fields extend the core wiki SCHEMA.md. Add them to entity pages as relevant.
See skills/llm-wiki-crm/templates/SCHEMA-crm-fields.md for a merge-ready patch.
Person Entity Additions
relationship_tier: strategic | active | watch | dormant
last_touchpoint: YYYY-MM-DD
meeting_cadence: daily | weekly | biweekly | monthly | quarterly | ad-hoc
next_meeting: YYYY-MM-DD # optional
influence_level: high | medium | low
enriched_at: YYYY-MM-DD # when auto-enrichment last ran
Company Entity Additions
relationship_tier: strategic | active | watch | dormant
account_health: green | yellow | red
last_touchpoint: YYYY-MM-DD
key_asks: [] # list of feature/product asks from this account
arr_tier: enterprise | mid-market | smb | prospect # optional, no dollar figures
enriched_at: YYYY-MM-DD # when auto-enrichment last ran
Tier Definitions
| Tier | Meaning |
|---|---|
strategic |
High-impact relationship. Flag if silent > 14 days. |
active |
Regular engagement. Flag if silent > 30 days. |
watch |
Relationship at risk or low-signal. Flag if silent > 60 days. |
dormant |
No active engagement. Informational only. |
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.
- 12d ago First seen · 172 lines · 58 tokens per session scan A 5b8499ed0dc4
llm-wiki-crm is a skill published in the GitHub repository anh-chu/llm-wiki-pm (6 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 2,065 once invoked, about $0.0003 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
llm-wiki
Build and maintain a persistent, interlinked Obsidian-compatible markdown wiki using Karpathy's LLM Wiki pattern. Extension-backed with auto-generated metadata, guardrails, and 14 custom tools (+3 opt-in agent-trajectory tools).
mindbase
Maintain a persistent AI-tended research wiki. Activates when the user wants to ingest a source (PDF, URL, article, paste), capture a thought, build the wiki context, query what's already known, lint for orphans/contradictions, or maintain page conventions. Phrases include "add this to my wiki", "today I decided…"…
wiki-ingest
Process source files into synthesised wiki pages. Always use this skill when the user says /wiki-ingest, 'import these files', 'process my clippings', 'ingest this article', 'I have new articles to add', 'turn this PDF into a wiki page', 'what's in my raw/ folder', or 'what have I ingested'. Also use when the user…
wiki-lint
Health-check the wiki: scan all pages for broken wikilinks, orphaned pages, stale index entries, missing connections, em-dash violations, orphaned assets, and schema errors. Produces a dated lint report. Always use this skill when the user says /wiki-lint, mentions broken links, dead wikilinks, orphaned pages, 'what's…
wiki-crystallize
Distil a chat thread, research session, or working document into a structured wiki page capturing the current state of knowledge. Always use this skill when the user says /wiki-crystallize, 'save this to my wiki', 'capture what we've worked out', 'write this up as a wiki page', 'update my wiki from this conversation'…
wiki-integrate
Weave a wiki page into the knowledge graph: add it to index.md and add backlinks in both directions. Always use this skill when the user says /wiki-integrate, 'nothing links to this page', 'this page is an orphan', 'connect this page to related pages', 'add backlinks to this page', 'add this page to the index', or…