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 matellez/claude-skills --skill first-90-days-demand-gen-revopsgit clone --depth 1 https://github.com/matellez/claude-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/matellez/claude-skills/first-90-days-demand-gen-revops)<a href="https://agentmods.dev/skills/matellez/claude-skills/first-90-days-demand-gen-revops"><img src="https://agentmods.dev/badge/skills/matellez/claude-skills/first-90-days-demand-gen-revops/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/matellez/claude-skills/first-90-days-demand-gen-revops"><img src="https://agentmods.dev/badge/skills/matellez/claude-skills/first-90-days-demand-gen-revops.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.00207 | $0.03170 |
| Opus 5 | $0.00103 | $0.01585 |
| Sonnet 5 | $0.00041 | $0.00634 |
| Haiku 4.5 | $0.00021 | $0.00317 |
Grade A, and why
first-90-days-demand-gen-revops 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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- first-90-days-demand-gen-revops — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
First 90 Days: Demand Gen and RevOps Leader Entry Plan
This skill builds a structured diagnostic and action plan for a demand gen or RevOps leader in a new role. The goal of the first 90 days is not to execute. It is to understand what exists, identify what is broken, build credibility with sales, and make one or two visible improvements before the first quarterly business review.
Leaders who skip the diagnostic phase and execute immediately on their prior playbook almost always solve the wrong problems. The company they just joined is not the last company. The ICP is different. The sales motion is different. The CRM is configured differently. The attribution model, if it exists at all, was built by someone with different assumptions. Execution without diagnosis accelerates the wrong things.
HOW TO SET UP THIS SKILL
This skill works out of the box. For more specific output, provide:
- The role title and whether it is demand gen, growth, RevOps, or hybrid
- Whether the function existed before you or you are building it from zero
- Company size, stage, and industry vertical
- Whether you inherited a team or are an individual contributor
- The first major meeting or deliverable you are working toward
- Any known problems you were hired to solve
The 90-Day Framework
The 90 days divide into three phases with different objectives.
Days 1-30: Listen and diagnose. Do not change anything yet. Days 31-60: Identify the highest-leverage fix and act on it. Days 61-90: Deliver one visible result and build the credibility to execute the full plan.
Days 1-30: The Diagnostic Phase
The goal of this phase is to build a complete picture of what exists, what is actually working, and what the organization believes is broken versus what is actually broken. These are often different things.
The CRM audit
This is the first thing to do. Before any stakeholder meeting, pull the CRM and understand what it is actually tracking versus what people think it is tracking. These are almost always different.
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.
- 12d ago First seen · 376 lines · 207 tokens per session scan A 479b4b80628f
first-90-days-demand-gen-revops is a skill published in the GitHub repository matellez/claude-skills (4 stars, last pushed 5mo ago), licensed MIT. It adds 207 tokens to every session and 3,170 once invoked, about $0.0010 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
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
market-research-workflow
Trigger for: federal acquisition market research; FAR Part 10 reports; refreshing an existing market research report; analyzing commerciality, competition, small-business availability, contract type, consolidation, prior awards, vendors, or market conditions; or preparing supported findings for a Pre-Award Agent. A…
acquisition-policy-workflow
Trigger for: explaining current FAR, DFARS, or agency-supplement text; determining documented acquisition-policy status for an agency and FAR part; comparing codified text, RFO model text, and agency deviations; tracing acquisition rulemaking; finding procurement comment periods; analyzing public comments; refreshing…
igce-builder-lh-tm
Trigger for: Labor-Hour IGCE, LH estimate, Time-and-Materials IGCE, T&M estimate, burdened hourly rate, burden multiplier, labor-category ceiling hours, materials estimate, proposed LH/T&M rate validation, price-reasonableness memo, or fair-and-reasonable analysis. Build auditable LH/T&M estimates using BLS OEWS…
rudder-data-graphs
Produces Data Graph YAML from RETL sources for Audiences. Use when designing Data Graphs, mapping RETL to entities/events, or assessing customer fit for Audiences.
rudder-typer-workflow
Generates type-safe SDKs (Swift/Kotlin) from tracking plans with compile-time validation. Use when generating type-safe event tracking code from tracking plans using RudderTyper.