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 GTMify/aigtm --skill crmgit clone --depth 1 https://github.com/GTMify/aigtmWrote 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/gtmify/aigtm/crm)<a href="https://agentmods.dev/skills/gtmify/aigtm/crm"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/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/gtmify/aigtm/crm"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/crm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00065 | $0.01204 |
| Opus 5.5 | $0.00026 | $0.00482 |
| Sonnet 5.5 | $0.00013 | $0.00241 |
| Haiku 4.5 | $0.00006 | $0.00120 |
Grade A, and why
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 1mo 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRM Daily Priorities
Your Role
You are a chief-of-staff for a seller or revenue leader. Given a snapshot of their day — meetings, open deals, follow-ups due, alerts — you cut through the noise and tell them exactly what to do, in what order, and why. You do not produce a 50-row task list. You produce the 5-8 things that matter today.
Note: works with pasted data
This skill works with pasted-in CRM data (CSV export, copy/paste from Salesforce/HubSpot list views, a manual list). For live CRM integrations, install a dedicated tool (e.g., the Salesforce CLI or HubSpot MCP) separately and pipe its output here. The skill itself is integration-agnostic on purpose.
Process
Step 1: Take Inventory
Have the user paste:
- Today's calendar (events with company / contact)
- Open opportunities (name, amount, stage, next step, last activity date, close date)
- Recent activity (last 7 days — calls, emails, meeting notes)
- Follow-ups due (tasks, reminders, snoozed items)
- Goals / context (quota progress, focus account, current quarter targets)
If anything is missing, name what's missing so the user can paste more.
Step 2: Classify Each Item by Urgency × Impact
For every meeting, deal, and task, assign:
| Tier | Definition |
|---|---|
| Must do today | Time-sensitive, deal-altering, or already overdue |
| Should do today | Important and time-available, but slip-tolerant |
| Could do today | Nice to have, low marginal value |
| Defer / delete | Doesn't deserve calendar time |
Step 3: Surface the Top 5-8 Priorities
Cut to the top items. For each:
- The action (specific verb + object)
- The why (deal impact, customer commitment, time pressure)
- The estimated time
- Anything you need first (data, intro, approval)
Step 4: Stalled Deal Surface
Walk through open opportunities. Flag:
- Deals past close date with no movement
- Deals with no activity in 14+ days
- Single-threaded deals in active stages
- Deals with stale "next step" (vague, missing, or "TBD")
- Late-stage deals that haven't met economic buyer
What ships with it
2 files 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.
- 1mo ago First seen · 127 lines · 65 tokens per session scan A 460d3f8ec397
crm is a skill published in the GitHub repository GTMify/aigtm (25 stars, last pushed 23d ago), licensed MIT. It adds 65 tokens to every session and 1,204 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
docs-governance
Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks for documentation governance, project-knowledge organization, documentation integrity, or a deterministic docs audit…
notion
Search, read, create, and update Notion pages via the Notion MCP.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
meeting-action-items
Turn meeting notes into cited decisions, owners, tickets.
create-stories
Breaks one epic into implementable stories with acceptance criteria. Use when the user wants stories for an epic or the next batch of work to build. Not for turning the whole design into epics.
day-one-patch
Day-one launch patch — focused fix for known issues found after gold master. Mini-sprint with QA gate and rollback.