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.
git clone --depth 1 https://github.com/studiomeyer-io/studiomeyer-marketplaceWrote 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/commands/studiomeyer-io/studiomeyer-marketplace/crm-contact)<a href="https://agentmods.dev/commands/studiomeyer-io/studiomeyer-marketplace/crm-contact"><img src="https://agentmods.dev/badge/commands/studiomeyer-io/studiomeyer-marketplace/crm-contact/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/commands/studiomeyer-io/studiomeyer-marketplace/crm-contact"><img src="https://agentmods.dev/badge/commands/studiomeyer-io/studiomeyer-marketplace/crm-contact.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.00014 | $0.00266 |
| Opus 5 | $0.00007 | $0.00133 |
| Sonnet 5 | $0.00003 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
crm-contact 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 6d 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.
What it actually says
The user wants to work with a contact: $ARGUMENTS
- Parse the argument. First word should be one of
add,update,search,show. If missing, default tosearch. - Based on the action:
- search: call
crm_searchwithquery: "<rest of args>"andentityTypes: ["contact"]. Show top 5 matches. - add: extract name, email, phone, company from the rest of the args. Call
crm_contactwithaction: "add". If company is mentioned but not in CRM, callcrm_companyfirst withaction: "create". - update: find the contact first with
crm_search. If multiple matches, ask which one. Then callcrm_contactwithaction: "update". - show:
crm_searchto find the contact, thencrm_get_timelinefor their history.
- search: call
- Confirm the action with one or two lines. Never dump the full contact record unless the user asked for it.
Match the user's language.
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.
- 6d ago Changed 6151e426bb66
- 11d ago First seen · 17 lines · 14 tokens per session scan A d1c47bb3805d
crm-contact is a command published in the GitHub repository studiomeyer-io/studiomeyer-marketplace (2 stars, last pushed 6d ago), licensed MIT. It adds 14 tokens to every session and 266 once invoked, about $0.0001 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 commands, from other repositories
status
Show memex statistics and status including projects, memos, and pending items.
open
Open the memex vault in Finder or Obsidian.
visibly-seo-potential
Potential analysis — empirical CTR model + realistic targets + lead/ROI calculation.
visibly-seo-status-quo
SEO Status-Quo analysis for a client — GSC + keyword cross-reference + quick wins.
visibly-seo-offer
Write a tailored SEO consulting offer from analysis + client context.
seo-fix
Applique les correctifs du dernier audit SEO/GEO, verifie que rien ne casse, et commit.