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 skills/tonydzi/second-brain-starter-kit/crm-syncnpx skills add tonydzi/second-brain-starter-kit --skill crm-syncgit clone --depth 1 https://github.com/tonydzi/second-brain-starter-kitWrote 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/tonydzi/second-brain-starter-kit/crm-sync)<a href="https://agentmods.dev/skills/tonydzi/second-brain-starter-kit/crm-sync"><img src="https://agentmods.dev/badge/skills/tonydzi/second-brain-starter-kit/crm-sync.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.00072 | $0.01582 |
| Opus 5 | $0.00036 | $0.00791 |
| Sonnet 5 | $0.00014 | $0.00316 |
| Haiku 4.5 | $0.00007 | $0.00158 |
Grade A, and why
crm-sync 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/crm-sync - keep the CRM knowledge layer fresh
The CRM (CHARM) is Anton's proven engine on GitLab. We reverse-engineered it once
(2026-06-19) into a linked vault layer so his digital twin can /ask how the CRM
works. Code keeps changing; this skill stops that knowledge from going stale silently.
It is the recurring half of the standing rule evaluate-recurring-into-routine.
What this is NOT: not a re-decompose-from-scratch. It is a DIFF-DRIVEN refresh: pull, see what changed, update only the notes that map to the changed code.
Where everything lives
- Code (read-only clone, 16 repos):
E:\CRM-app(memorycrm-gitlab). - Decomposition audit (HTML, source of the notes):
E:\CRM-app\_AUDIT\(Functional-Map.html,Know-How-Decomposition.html,Architecture-Deep.html). - Vault knowledge layer:
$OBSIDIAN_VAULT/05-Resources/CRM-Engine/_CHARM-CRM-Engine-MOC.md(hub)crm-architecture-4-layers.mdcrm-mtproto-engine.mdcrm-core-autopilot.mdcrm-admin-panel-api-brain.mdcrm-data-model-mongo.mdcrm-know-how-13-patterns.mdcrm-landing-api-money.md- decision:
$OBSIDIAN_VAULT/02-Decisions/decision-crm-keep-cc-drop-decide.md
Repo -> note map (which note to refresh when which code changes)
| Code area in E:\CRM-app | Note(s) to refresh |
|---|---|
admin-panel / admin-panel-api (FastAPI brain, filter-DSL, $facet) |
crm-admin-panel-api-brain |
mtproto-api (Telethon hands, event-pool, dialog export, FloodWait) |
crm-mtproto-engine |
core (aiocron autopilot: newsletters, gatekeeper, tapping, calls) |
crm-core-autopilot |
landing-api (token sale, NOWPayments, CHEATING_MODE, webhook) |
crm-landing-api-money |
| shared models / Mongo schema (collections, fields) | crm-data-model-mongo |
| cross-cutting architecture / generations | crm-architecture-4-layers |
| reusable patterns / know-hows | crm-know-how-13-patterns |
| any capability added/removed/disabled | decision-crm-keep-cc-drop-decide (+ MOC) |
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 · 98 lines · 72 tokens per session scan A b718aa3ac278
crm-sync is a skill published in the GitHub repository tonydzi/second-brain-starter-kit (5 stars, last pushed 6d ago), licensed MIT. It adds 72 tokens to every session and 1,582 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-31.
Other skills, from other repositories
autoresearch
Run a bounded, source-grounded research loop, draft a cited dossier, and optionally propose a separately reviewed canonical vault merge. Use when the user wants autonomous or deep research that may access the public web. Triggers: /autoresearch, autoresearch, research this topic, deep dive into, investigate, find…
wiki-ingest
Ingest supplied source material into an Obsidian vault with provenance and claim tracking: pasted text, files staged in the selected vault's inbox or .raw archive, or explicitly approved URLs. Use for a single source or bounded batch, not for saving an assistant answer. Triggers: ingest, ingest this file, ingest this…
canvas
Create, inspect, and update Obsidian JSON Canvas boards with text, file, link, group, and edge nodes. Use for canvas status, canvas lists, visual maps, zones, spatial layouts, adding vault notes or media to a .canvas file, and requests such as create canvas, add to canvas, or put this on the canvas.
defuddle
Plan and, with explicit network consent, use an optional external Defuddle cleaner to extract article-like HTTPS pages as Markdown. Use for defuddle, clean this URL, strip page clutter, readable Markdown from a web page, or preparing a web source for later wiki ingestion.
obsidian-bases
Explain, draft, and validate Obsidian Bases .base files with filters, formulas, properties, summaries, and table, card, or list views. Use for Obsidian Bases, database-like vault views, dynamic tables, reading lists, task trackers, filters, formulas, summaries, and .base file edits.
save
Save a user-selected answer, decision, insight, or session summary into an Obsidian vault as one reviewed transaction. Use only when the user explicitly asks to preserve specific conversation content, not when they supply a file or URL to ingest. Triggers: /save, save this, save that answer, file this conversation…