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 ArrowsHQ/arrows-sales-skills --skill arrows-crm-hygienegit clone --depth 1 https://github.com/ArrowsHQ/arrows-sales-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/arrowshq/arrows-sales-skills/arrows-crm-hygiene)<a href="https://agentmods.dev/skills/arrowshq/arrows-sales-skills/arrows-crm-hygiene"><img src="https://agentmods.dev/badge/skills/arrowshq/arrows-sales-skills/arrows-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/arrowshq/arrows-sales-skills/arrows-crm-hygiene"><img src="https://agentmods.dev/badge/skills/arrowshq/arrows-sales-skills/arrows-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.00220 | $0.14755 |
| Opus 5.5 | $0.00088 | $0.05902 |
| Sonnet 5.5 | $0.00044 | $0.02951 |
| Haiku 4.5 | $0.00022 | $0.01476 |
Grade A, and why
arrows-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 2d 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 — 596 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Learns how the person's CRM and pipeline really work, saves that as a guide, and keeps the CRM matching it. Works with whatever CRM is connected, or a CSV export.
| You get | What's in it |
|---|---|
arrows-crm-guide.md |
Built on the first run and saved to the project: the stages and how deals really move between them, where they stall, which fields to update after each call or milestone, what each stage needs, and which fields go unused. Every Sales Skill can read it, so follow-ups and deal updates touch the right fields |
| Hygiene score | Every run: a score for each category below, with counts, and one overall score |
| Worst deals | The deals with the most problems (and, for sales leaders, each rep's score and most common gap) |
| Updates I can make | A ready-to-apply list in small sets, each named for what it fixes. Every update shows its evidence ("Competitor: [Competitor], mentioned on the [date] call") |
| Category | What fails |
|---|---|
| Close dates | Open deals with no close date, or one in the past |
| Next steps | Open deals with no next step and no upcoming task, meeting or activity |
| Required fields | Fields the guide requires (for every deal, or by stage) that are empty, usually amount and source plus what each stage adds; and recently lost deals with no loss reason |
| Stage vs. activity | The stage says something happened that the record, calls and emails don't show ("Proposal" with no proposal sent) |
| Contacts | Deals with no contact associated |
| Duplicates | Companies or contacts that are the same one entered twice |
| Fill from calls and email | Fields that are empty or out of date where a call or email has the answer: a competitor named, a new stakeholder, an amount or timeline the buyer gave |
The person replies at most twice before seeing results: once on the first run to confirm the guide, then once per set of updates they want made. Nothing in the CRM changes until they approve the exact changes.
Step 1: Find the guide
Look in the project for arrows-crm-guide.md (an older copy may be called arrows-crm-standards.md; use it the same way), and read the profile files (especially ## Pipeline stages and ## Discovery and qualification in arrows-sales-process.md, and ## Every rep, every deal in arrows-how-we-work.md if present).
- Guide found: use it and go to Step 3. Don't re-confirm it. If the CRM has changed since (a field or stage it names no longer exists, a new pipeline), say so in one line at the top of the report and offer "Refresh my CRM guide."
- No guide (first run): go to Step 2. Setup leaves CRM depth to this skill, so this is expected. If this chat shows the guide was built before but it isn't in the project, rebuild it and remind them in one line to save it, so they aren't asked to confirm it every week.
Rep or leader. Use ## About me in arrows-how-i-work.md. Without it, match the person's email to a CRM owner: owns most open deals → rep; others own most and they own few → leader; a real share of both → both. A leader's scope is their team's deals (from team or role data, or the owners of deals they've been involved in over the last 90 days), never the whole company unless that's all you can tell; then label it "company-wide." The scope input, if given, wins.
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.
- 2d ago Changed · -90 tokens per session 305b161ca2c5
- 4d ago First seen · 596 lines · 310 tokens per session scan A ae4a67bf4e9b
arrows-crm-hygiene is a skill published in the GitHub repository ArrowsHQ/arrows-sales-skills (4 stars, last pushed 3d ago), licensed Apache-2.0. It adds 220 tokens to every session and 14,755 once invoked, about $0.0009 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-10-06.
Other skills, from other repositories
evm
Help users answer one question: "Are we on track?" using Earned Value Management metrics. This skill replaces gut-feel status reporting and traffic-light dashboards with four computed numbers (SV, SPI, CV, CPI) that tell you exactly where a project stands — in schedule and in budget — at any point in time.
geo-prospect
CRM-lite for managing GEO agency prospects and clients. Track leads through the full sales pipeline: Lead → Qualified → Proposal Sent → Won → Lost. Store audit history, notes, deal values, and generate pipeline summaries. Use when user says "prospect", "lead", "client", "pipeline", "crm", "nuovo prospect", "aggiungi…
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
meeting-to-deal
Turn meeting transcripts into deal updates — key points, commitments, and next steps posted to matching CRM deals automatically. Auto-creates contacts for new attendees. Use when someone says "log my meetings to deals", "update CRM from calls", "what did I commit to in meetings", "sync notetaker", "log this meeting"…
syndic
Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…
customer-onboarding-and-implementation
Takes a new customer from signature to working — setting a definition of live that both sides agreed before the contract was signed, planning and staffing the implementation, running data migration and integration realistically, training the people who will actually use it, and handing over to the ongoing…