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 oncesylvia/fundraising-skills --skill pipeline-trackergit clone --depth 1 https://github.com/oncesylvia/fundraising-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/oncesylvia/fundraising-skills/pipeline-tracker)<a href="https://agentmods.dev/skills/oncesylvia/fundraising-skills/pipeline-tracker"><img src="https://agentmods.dev/badge/skills/oncesylvia/fundraising-skills/pipeline-tracker/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/oncesylvia/fundraising-skills/pipeline-tracker"><img src="https://agentmods.dev/badge/skills/oncesylvia/fundraising-skills/pipeline-tracker.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.00093 | $0.00972 |
| Opus 5 | $0.00046 | $0.00486 |
| Sonnet 5 | $0.00019 | $0.00194 |
| Haiku 4.5 | $0.00009 | $0.00097 |
Grade A, and why
pipeline-tracker 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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fundraising pipeline tracker
A raise is a sales process, and the founder is running it against time. Momentum is everything: a tight, parallel process creates urgency; a slow, serial one leaks energy and signals weakness. This skill sets up and maintains a simple file-based CRM so nothing falls through and the founder always knows the next action.
Read shared/references/outreach-ethics.md — follow-up discipline here must stay
on the right side of persistent-vs-pestering.
Set it up (first run)
Create a tracker file in the user's project (default:
fundraising-pipeline.csv, or Markdown table if they prefer). Use the template
in references/pipeline-template.md. Columns:
| Field | What it holds |
|---|---|
| Investor | Firm or angel name |
| Partner | The specific person you're working |
| Tier | A / B / C (from investor-targeting) |
| Stage | Pipeline stage (see below) |
| Source | How you got in (warm intro via X / cold / inbound) |
| Last contact | Date of last touch |
| Next action | The single next thing you owe |
| Next action date | When to do it |
| Check / interest | Indicated check size or interest level |
| Notes | Anything said — objections, who they cc'd, asks |
Pipeline stages
Keep it simple and linear; every investor sits in exactly one:
- Researched — qualified as a fit, not yet contacted.
- Contacted — first outreach sent (cold or intro requested).
- Engaged — they replied / a call is booked.
- Met — first meeting done.
- Diligence — follow-up meetings, data room, partner meeting.
- Term sheet / Committed — verbal or written commitment.
- Passed — they said no (record why — it's signal).
- Dormant — no response after the follow-up sequence ended.
Running it (ongoing)
When the founder gives an update ("had a call with X", "Y passed", "Z asked for the deck"), you:
- Update the row — move the stage, set Last contact, write the Notes.
- Set the next action + date — every active investor must have a next action owned by the founder. No row in stages 2–6 should have an empty next action.
- Surface what's due — list who needs a follow-up today/this week, and draft
it via the
cold-emailorwarm-introskill if asked. - Watch the funnel — report simple counts (e.g., 24 researched, 11 contacted, 4 met, 1 in diligence) so the founder sees conversion and knows whether to add more top-of-funnel.
What ships with it
1 file 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.
- 12d ago First seen · 84 lines · 93 tokens per session scan A 90088b394b54
pipeline-tracker is a skill published in the GitHub repository oncesylvia/fundraising-skills (4 stars, last pushed 2mo ago), licensed MIT. It adds 93 tokens to every session and 972 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-08-31.
Other skills, from other repositories
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…
cashflow-forecaster
Forecast construction project cash flow. Project income and expenses, identify funding gaps, and optimize payment timing for improved financial management.
cwicr-change-order
Process construction change orders using CWICR data. Calculate cost impact, compare to original estimate, and generate change order documentation.
cwicr-schedule-integrator
Integrate CWICR cost data with project schedules. Link work items to schedule activities, generate cost-loaded schedules, and cash flow projections.
cwicr-subcontractor
Analyze and compare subcontractor bids against CWICR benchmarks. Evaluate pricing, identify outliers, and support negotiation.
cash-flow-forecaster
Forecast project cash flow based on schedule and cost data. Generate S-curves and payment projections.