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 event4u-app/agent-config --skill build-buy-partnergit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/build-buy-partner)<a href="https://agentmods.dev/skills/event4u-app/agent-config/build-buy-partner"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/build-buy-partner/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/event4u-app/agent-config/build-buy-partner"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/build-buy-partner.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.00039 | $0.02312 |
| Opus 5 | $0.00019 | $0.01156 |
| Sonnet 5 | $0.00008 | $0.00462 |
| Haiku 4.5 | $0.00004 | $0.00231 |
Grade A, and why
build-buy-partner 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 11d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
build-buy-partner
When to use
- A capability gap exists and the question is whether to build internally, buy a vendor / acquisition, or partner.
- An "obviously build" choice has crept in by default; the question is whether it survives a deliberate compare.
- A vendor / partner relationship is up for renewal; the question is whether to keep buying, switch, or insource.
- An acquisition has been floated; the question is whether the integration cost justifies the speed-to-capability.
Do NOT use for vendor selection within a "buy" decision (different skill), market-entry beachhead choice (route to market-entry-analysis (P2)), or scenario-shape comparison (route to scenario-modeling (O4); P1 consumes O4's bundle).
Cognition cluster
- Mental model 28 — Inversion. "What would force us to undo this choice in 18 months?" Inversion surfaces the dependency-risk and integration-cost that the forward case understates. See
mental-models.md§ 28. - Mental model 21 — Second-order thinking. Each option chains: build → ongoing maintenance + opportunity cost; buy → integration + lock-in; partner → dependency + boundary management. Single-order "build is cheaper" fails on the second-order. See
mental-models.md§ 21. - Mental model 26 — Optionality. Read each option by which choices it preserves (switch costs, re-build optionality, re-negotiation power) vs forecloses. The option with bounded foreclosure usually wins. See
mental-models.md§ 26. - Context-spine — org-stage + product + customer-segment. Read org-stage for capacity (pre-seed should buy almost everything non-core; growth-stage can build deeper). Read product for whether the capability is core-differentiation (build) or commodity (buy). Read customer-segment for whether enterprise-segment buyers require a build-it-yourself story.
Procedure
Step 0: Frame the capability as core vs commodity
Two questions:
- Is this capability a differentiator for our customers? If yes → build-bias. If no → buy-bias.
- Does it sit on the critical path of our product? If yes + differentiator → build. If yes + commodity → buy. If no → partner.
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.
- 11d ago First seen · 153 lines · 39 tokens per session scan A 1965752c933a
build-buy-partner is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 2,312 once invoked, about $0.0002 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
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
same-set-reusable-flow-for-project-file-inventor
Reusable MetaKim file inventory classification flow. It helps separate durable sources, generated evidence, runtime mirrors, temporary state, and risky unknowns before cleanup or commit.
meta-theory
MetaKim executable governance dispatcher. It classifies the run, loads only needed references, preserves foundational capabilities and runtime-native abilities, routes owner + weapon + dependency + runtime + OS + verification, and closes only with evidence, intent acceptance, and writeback decision.
starreel-drama-production
Operating skill for any AI agent driving the StarReel short-drama production pipeline (script → rewrite → extract → portraits + sheets → storyboards → frames → video → voiceover → final cut) over MCP or REST. Covers the ordered workflow, the entry-point decision table (which channel each kind of customer material…
seedance-20
Generate and direct cinematic AI videos with Seedance 2.0 (ByteDance/Dreamina/Jimeng). Covers text-to-video, image-to-video, video-to-video, and reference-to-video workflows with @Tag asset references, multi-character scenes, audio design, and post-processing. Use when making AI video, writing Seedance prompts…
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.