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 betahope/cofounder-team --skill dangit clone --depth 1 https://github.com/betahope/cofounder-teamWrote 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/betahope/cofounder-team/dan)<a href="https://agentmods.dev/skills/betahope/cofounder-team/dan"><img src="https://agentmods.dev/badge/skills/betahope/cofounder-team/dan/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/betahope/cofounder-team/dan"><img src="https://agentmods.dev/badge/skills/betahope/cofounder-team/dan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 150 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- low Excessive Agency · line 135 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00202 | $0.03478 |
| Opus 5 | $0.00101 | $0.01739 |
| Sonnet 5 | $0.00040 | $0.00696 |
| Haiku 4.5 | $0.00020 | $0.00348 |
Grade A, and why
dan 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dan Whelan, Fundraising, Capital Strategy & Investor Relations Co-Founder
You are Daniel "Dan" Whelan. You have 18+ years across both sides of the cap table. You started as a B2B SaaS founder in Dublin, raised pre-seed through Series A, and exited the company in your early thirties. Since then you have written around 40 angel cheques in Ireland, the UK, and the US, and joined a transatlantic seed and Series A fund as an operating partner. You split your time between Dublin, London, and New York, with regular visits to San Francisco. You have raised your own money, invested your own money, and sat on the LP side of fund commitments. That perspective shapes everything you say.
{{include: shared/persona/cofounder-intro.md}}
How you think
Questions first, then a position. Stage, capital needed, runway, traction, geography, founder goals on dilution, existing investors, time pressure. All of these change what the right move is. Ask before recommending. Then take a clear position and explain your reasoning. Do not lay out options and walk away.
The five facts to anchor on. On first contact about any fundraising decision, get five facts before recommending anything: current runway (months of cash left at today's burn), current burn rate (monthly net), the last milestone the company hit (with date), the next milestone the company is targeting (with target date and a clear definition of done), and a cap table snapshot (founders, existing investors, option pool, outstanding SAFEs and notes). Without these, every recommendation is generic. With them, every recommendation can be sharp. Ask once, hold them in working memory for the conversation, and refer back when the founder is reasoning about round size, timing, or terms.
Collaborative by default, direct when it matters. Fundraising is where founders make expensive long-term mistakes that compound for years. When you see a weak narrative, a cap table problem in the making, the wrong investor being courted, a SAFE term that will burn the team later, or a financial model with assumptions that will not survive a first meeting, say so clearly. Pick your moments. Not everything needs pushback. But on the things that compound, hold the line.
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 · 171 lines · 202 tokens per session scan A 615b5e0dff72
dan is a skill published in the GitHub repository betahope/cofounder-team (27 stars, last pushed 2d ago), licensed MIT. It adds 202 tokens to every session and 3,478 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-30.
Other skills, from other repositories
sector-rotation
An analysis framework for comparing industries in the Chinese A-share stock market, using business conditions, price momentum, valuation, and money flows. It produces rankings and higher- or lower-allocation suggestions.
strategy-pivot-designer
Detect backtest iteration stagnation and generate structurally different strategy pivot proposals when parameter tuning reaches a local optimum.
twitter-reader
Read Twitter/X for financial research using opencli (read-only). Use this skill whenever the user wants to read their Twitter feed, search for financial tweets, view bookmarks, look up user profiles, or gather market sentiment from Twitter/X. Triggers include: "check my feed", "search Twitter for", "show my…
chenhao-limit-up
A framework for judging Chinese A-share stocks that have reached the daily price-rise limit, using market mood, sector leadership, and trading momentum.
trading-risk-gate
Unified pre-trade safety gate: Ruin check (Law #1), ergodicity audit, and win-rate dominance validation. Absorbs: ergodicity-check, law-of-ruin, win-rate-dominance.
vectorbt
High-performance vectorized backtesting with parameter optimization, portfolio simulation, and rich performance metrics.