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 cofounder-team-upgradegit 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/cofounder-team-upgrade)<a href="https://agentmods.dev/skills/betahope/cofounder-team/cofounder-team-upgrade"><img src="https://agentmods.dev/badge/skills/betahope/cofounder-team/cofounder-team-upgrade/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/cofounder-team-upgrade"><img src="https://agentmods.dev/badge/skills/betahope/cofounder-team/cofounder-team-upgrade.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Agent Snooping · line 28 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00113 | $0.00719 |
| Opus 5 | $0.00056 | $0.00360 |
| Sonnet 5 | $0.00023 | $0.00144 |
| Haiku 4.5 | $0.00011 | $0.00072 |
Grade A, and why
cofounder-team-upgrade 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.
What it actually says
Upgrade the cofounder-team skills
When the user asks to upgrade, do exactly this. Do not edit any files. Only run shell commands.
-
Set the repo folder. Default is
~/.cofounder-team. If that folder does not exist, ask the user where they cloned the repo and use that path instead for the rest of the steps. -
Record the current version so we can show the user what changed:
git -C ~/.cofounder-team rev-parse HEADRemember this value as
OLD. -
Pull the latest version:
git -C ~/.cofounder-team pull -
Re-run the installer so the skills are rebuilt and linked into
~/.claude/skills/:bash ~/.cofounder-team/setupsetupnow compiles the source into the finished skills first (a plain-bash build, no extra tools to install), then links the Claude Code build. The build runs automatically as part ofsetup; there is no separate command. This is why an upgrade always re-links: it repoints each skill in~/.claude/skills/at the freshly built version, even for users who installed before the build step existed. -
Show what changed since
OLD. First the curated changelog, then the raw commit log as a fallback.Changelog diff (this is the human-readable summary of what shipped):
git -C ~/.cofounder-team diff OLD..HEAD -- CHANGELOG.mdIf the user was on a version before
CHANGELOG.mdexisted (anything older than v0.2.0), the diff will show the whole changelog as added. That is correct: everything in it is new to them.Raw commit log (covers anything not captured in the changelog):
git -C ~/.cofounder-team log --oneline OLD..HEAD(Replace
OLDwith the value from step 2 in both commands.)If there are no new commits, tell the user they are already up to date.
-
Tell the user the new version and to start a new Claude Code session so the updated skills load. Read the version from
~/.cofounder-team/VERSIONif it exists; otherwise just tell them to restart.
That is the entire upgrade workflow. Do not run additional commands, do not edit files, do not modify anything outside ~/.cofounder-team and ~/.claude/skills/.
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 · 53 lines · 113 tokens per session scan A 84d95c331cb8
cofounder-team-upgrade is a skill published in the GitHub repository betahope/cofounder-team (28 stars, last pushed 5d ago), licensed MIT. It adds 113 tokens to every session and 719 once invoked, about $0.0006 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…