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 fundraising-process-mappinggit 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/fundraising-process-mapping)<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/fundraising-process-mapping"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/fundraising-process-mapping/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/fundraising-process-mapping"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/fundraising-process-mapping.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.00104 | $0.03560 |
| Opus 5 | $0.00052 | $0.01780 |
| Sonnet 5 | $0.00021 | $0.00712 |
| Haiku 4.5 | $0.00010 | $0.00356 |
Grade A, and why
fundraising-process-mapping 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fundraising Process Mapping
This skill activates when a practitioner needs to design or document the fundraising lifecycle in Salesforce — mapping donor cultivation, solicitation, and stewardship phases to Opportunity stages and sales processes in either NPSP (legacy) or Nonprofit Cloud (NPC). It covers the NPSP four-process model, the NPC stage model divergence, Moves Management alignment, and the decision framework for stage design across fundraising program types. It does NOT cover how to configure Engagement Plans, process gift entries, integrate payment processors, or manage recurring donations.
Before Starting
Gather this context before working on anything in this domain:
- Confirm the platform — Determine whether the org is on legacy NPSP (the managed package, now end-of-life for new installs as of December 2025) or Nonprofit Cloud (NPC, the next-generation native Salesforce offering). The stage configuration approach, available objects, and feature availability differ materially between the two. If the org was created after December 2025 and does not have the
npspnamespace in Setup > Installed Packages, it is on NPC or a blank org, not NPSP. - Identify program types — NPSP ships four pre-configured Opportunity sales processes: Donation, Grant, In-Kind, and Major Gift. Each has a distinct stage picklist sequence. Confirm which program types the organization runs and whether all four are needed or only a subset.
- Understand who owns each stage — Solicitation and stewardship stages often have different responsible roles (prospect researcher, gift officer, stewardship coordinator). Mapping stage ownership prevents ambiguity about when a record moves and who is accountable.
- Establish the probability model — Salesforce displays a Probability % field on Opportunity that forecasts pipeline value. Nonprofits using pipeline reports depend on accurate probabilities per stage. Gather any existing probability targets before designing stages.
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 · 206 lines · 104 tokens per session scan A 2af4effd99be
fundraising-process-mapping is a skill published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 104 tokens to every session and 3,560 once invoked, about $0.0005 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
Grant Writer
Craft compelling grant proposals that secure funding for nonprofits and research.
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.
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.
v3-use-utils
Documentation for reusable utility functions in a project, including validation, date formatting, CSS variables, permissions, local storage, and tokens.