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 guia-matthieu/clawfu-skills --skill crm-hygienegit clone --depth 1 https://github.com/guia-matthieu/clawfu-skillsWrote 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/guia-matthieu/clawfu-skills/crm-hygiene)<a href="https://agentmods.dev/skills/guia-matthieu/clawfu-skills/crm-hygiene"><img src="https://agentmods.dev/badge/skills/guia-matthieu/clawfu-skills/crm-hygiene/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/guia-matthieu/clawfu-skills/crm-hygiene"><img src="https://agentmods.dev/badge/skills/guia-matthieu/clawfu-skills/crm-hygiene.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.00025 | $0.02970 |
| Opus 5 | $0.00013 | $0.01485 |
| Sonnet 5 | $0.00005 | $0.00594 |
| Haiku 4.5 | $0.00003 | $0.00297 |
Grade A, and why
crm-hygiene 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 9d 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 — 418 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRM Hygiene
Systematically identify and resolve data quality issues in your CRM to improve forecast accuracy, reporting, and automation reliability.
When to Use This Skill
- Quarterly CRM audits
- Before major reporting periods
- When automation workflows fail
- After team changes or migrations
- Preparing for CRM integrations
Methodology Foundation
Based on Salesforce Data Quality Best Practices and RevOps Co-op Data Governance frameworks, focusing on:
- Completeness (required fields populated)
- Consistency (standardized values)
- Accuracy (correct and current data)
- Timeliness (recent updates)
What Claude Does vs What You Decide
| Claude Does | You Decide |
|---|---|
| Defines audit criteria | Which fields are required |
| Identifies data issues | Priority of fixes |
| Categorizes problems by type | Who owns cleanup tasks |
| Suggests remediation steps | Automation vs manual fix |
| Creates cleanup reports | Enforcement policies |
What This Skill Does
- Audit design - Define required fields and validation rules
- Issue identification - Find missing, inconsistent, duplicate data
- Prioritization - Rank issues by business impact
- Remediation planning - Action steps to fix issues
- Governance recommendations - Prevent future issues
How to Use
For Audit Design:
Help me create a CRM hygiene audit for [CRM System].
Key objects to audit:
- [Leads, Contacts, Accounts, Opportunities]
Critical fields for each:
- Leads: [list required fields]
- Opportunities: [list required fields]
Our main issues:
- [Describe known problems]
For Data Audit:
Audit this opportunity data for hygiene issues:
[Paste export or describe data]
Required fields:
- [List fields that must be populated]
Validation rules:
- [List rules like "Stage must match Amount > $0"]
Instructions
Step 1: Define Audit Scope
Object Priority (typical):
- Opportunities - Revenue impact
- Accounts - Relationship foundation
- Contacts - Communication accuracy
- Leads - Pipeline source
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.
- 9d ago First seen · 418 lines · 25 tokens per session scan A 088bb8bc7501
crm-hygiene is a skill published in the GitHub repository guia-matthieu/clawfu-skills (149 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 2,970 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-09-03.
Other skills, from other repositories
after-action-report
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event.…
azure-devops
Manage Azure DevOps projects, work items, repos, PRs, pipelines, wikis, test plans, security alerts, variable groups, environments/approvals, branch policies, and attachments. Use when user asks to: manage sprints, create/update work items, list repos, create PRs, run pipelines, search code, manage wiki pages, check…
ads-performance-analytics
How to read paid media dashboards without fooling yourself. Attribution models, platform reporting quirks, multi-platform reconciliation, ROAS vs LTV horizon traps, statistical noise in performance metrics, incrementality testing, and the failure modes that produce expensive lessons. Triggers on read paid media…
okr-design
OKR design as actually shipped, not as conference-talk theory. Outcome statements that drive decisions, key results that measure the right thing, scoring discipline, mid-quarter recalibration, and the difference between sandbagged OKRs (always 100%) and aspirational OKRs (always 30%) and stretch OKRs (genuine ambition…
paid-media-strategy
A discipline for running paid media that does not light money on fire. Hypothesis writing for paid spend, channel selection, budget allocation, audience targeting, bid strategy, campaign types, what NOT to spend on, attribution reality, and the failure modes that produce expensive lessons. Triggers on paid media…
onboard
Sets up ai-toolkit in a project: symlinks, CLAUDE.md, intent interview. Triggers: onboard, setup project, install ai-toolkit, migrate project.