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 BanibrataChatterjee/AwesomeSalesforceSkills --skill donor-lifecycle-requirementsgit clone --depth 1 https://github.com/BanibrataChatterjee/AwesomeSalesforceSkillsWrote 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/banibratachatterjee/awesomesalesforceskills/donor-lifecycle-requirements)<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/donor-lifecycle-requirements"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/donor-lifecycle-requirements/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/banibratachatterjee/awesomesalesforceskills/donor-lifecycle-requirements"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/donor-lifecycle-requirements.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.00068 | $0.02402 |
| Opus 5 | $0.00034 | $0.01201 |
| Sonnet 5 | $0.00014 | $0.00480 |
| Haiku 4.5 | $0.00007 | $0.00240 |
Grade A, and why
donor-lifecycle-requirements 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Donor Lifecycle Requirements
This skill activates when you need to map the full donor lifecycle in NPSP or Nonprofit Cloud — from prospect acquisition through cultivation, upgrade, and lapsed re-engagement. It produces lifecycle stage maps, Moves Management configuration requirements, segmentation designs, and upgrade path workflows grounded in NPSP/NPC platform capabilities.
Before Starting
Gather this context before working on anything in this domain:
- NPSP vs NPC: As of December 2025, NPSP is no longer offered in new production orgs. New nonprofits use Nonprofit Cloud (NPC). Legacy orgs remain on NPSP. The donor lifecycle features differ — confirm which platform before designing workflows.
- Moves Management is NPSP-specific in its classic form: NPSP Moves Management uses Opportunity Stages mapped to cultivation stages on a Contact or Opportunity. NPC uses a portfolio management approach. These are different design paradigms.
- LYBUNT/SYBUNT are NPSP report concepts: LYBUNT (Last Year But Unfortunately Not This Year) and SYBUNT (Some Year But Unfortunately Not This Year) are standard NPSP report labels for lapsed donors. These reports are built on Opportunity data in NPSP. NPC has Actionable Segmentation for donor classification.
- Segmentation ≠ Marketing Automation: Donor segmentation in this context means portfolio classification for relationship management — who goes in the Annual Fund, Mid-Level, or Major Gift portfolio. This is NOT campaign management or email marketing execution.
Core Concepts
NPSP Moves Management
NPSP Moves Management maps the donor cultivation lifecycle through Opportunity Stage picklist values and a Contact-level field tracking the donor's current cultivation stage. The lifecycle is:
Prospect → Identified → Cultivating → Solicited → Closed Won (or Lost)
Configuration components:
- Opportunity Stage picklist values aligned to cultivation stages
- Opportunity Sales Process restricting stages per Opportunity Record Type
- Path component on Opportunity layout showing stage progression
- Custom reports on Opportunity Stage changes for portfolio review
What ships with it
6 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.
- 9d ago First seen · 180 lines · 68 tokens per session scan A 9bb25282c027
donor-lifecycle-requirements is a skill published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 68 tokens to every session and 2,402 once invoked, about $0.0003 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
html-ppt-zhangzara-bold-poster
OpenDesign's Series A growth story: the traction curve, the expansion motion, and why it's venture-scale. Built as a decision-grade fundraising pitch deck for Series A partners.
background
Use when the user wants to see, inspect, cancel, or prune background agents fired during prior chain runs. Read/manage .hyperflow/background/registry.json and the per-agent output buffers at .hyperflow/background/ .md. Standalone — never auto-invoked. Trigger with /hyperflow:background, "list background agents"…
flush
Use when the user wants to manually flush a deferred-commit queue from a prior or interrupted chain. Reads .hyperflow/commits-queue/manifest.json, fast-forwards the staging branch onto the user's branch, deletes staging, clears the queue. Recovery interface when a chain crashed before its Step 4 auto-flush ran.…
v3-create-crud
A page generator for standard create, read, update, and delete screens, commonly called CRUD screens. It uses Element Plus, a Vue user-interface library, to build tables, searches, pagination, forms, and delete confirmations.
hunt-django
Hunt Django-specific vulnerabilities: DRF permission gaps, ORM injection, and admin exploitation.
v3-use-composables
Documentation for reusable Vue functions in a project, covering device detection, asynchronous dropdown data, loading screens, pagination, routing, themes, page titles, and watermarks.