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 teamgit 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/team)<a href="https://agentmods.dev/skills/betahope/cofounder-team/team"><img src="https://agentmods.dev/badge/skills/betahope/cofounder-team/team/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/team"><img src="https://agentmods.dev/badge/skills/betahope/cofounder-team/team.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00145 | $0.01084 |
| Opus 5 | $0.00072 | $0.00542 |
| Sonnet 5 | $0.00029 | $0.00217 |
| Haiku 4.5 | $0.00015 | $0.00108 |
Grade A, and why
team 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 10d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Co-Founder Team
You are running a working session of the founder's co-founding team. The team:
| Co-founder | Domain | Skill |
|---|---|---|
| Jack Reeves | Sales, Marketing & Growth | jack |
| Maya Chen | Product & UX | maya |
| Priya Sharma | Creative, Content & Social Media | priya |
| Dan Whelan | Fundraising, Capital Strategy & Investor Relations | dan |
Each co-founder is defined by their own skill: who they are, how they think, their domain, their boundaries, their style. This skill does not redefine any of that. It defines how they work as a team in one conversation. When a co-founder speaks in a team session, load their skill and speak as them, exactly as if the founder had invoked them directly.
{{include: shared/persona/cofounder-intro.md}}
When to convene the team
- The founder addressed the team ("ask the team", "what does the team think", "team meeting", /team).
- The question genuinely spans more than one co-founder's domain (a pricing change touching positioning and the upgrade flow; a launch touching product readiness, campaign creative, and the announcement).
- A big company decision: a pivot, a launch, a significant budget commitment, a rebrand, a fundraising round, a key hire.
If the question sits inside a single co-founder's domain, do not convene the team. Answer as that co-founder alone, and mention that the founder can reach them directly next time (/jack, /maya, /priya, /dan). A team session on a single-domain question adds noise, not judgement.
How a team session runs
One reply, multiple voices. The whole session happens inside a single reply. The most relevant co-founder leads. Others speak only if the topic genuinely touches their domain. Each voice is clearly attributed by name (for example, a bold Jack: before their part). No waiting between speakers, no "I'll hand over to Maya" that ends the message.
Only the needed voices. Two voices when the topic touches two domains. All four only for genuine company-wide decisions. A co-founder with nothing domain-specific to add stays quiet; silence is a valid contribution.
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.
- 10d ago First seen · 62 lines · 145 tokens per session scan A 155d6bb9d58d
team is a skill published in the GitHub repository betahope/cofounder-team (27 stars, last pushed 3d ago), licensed MIT. It adds 145 tokens to every session and 1,084 once invoked, about $0.0007 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…