Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add int2t05/engineering-skills/plugin install engineering-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/int2t05/engineering-skills/oss-strategy)<a href="https://agentmods.dev/skills/int2t05/engineering-skills/oss-strategy"><img src="https://agentmods.dev/badge/skills/int2t05/engineering-skills/oss-strategy.svg" alt="Measured on agentmods" 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.00067 | $0.01102 |
| Opus 5 | $0.00034 | $0.00551 |
| Sonnet 5 | $0.00013 | $0.00220 |
| Haiku 4.5 | $0.00007 | $0.00110 |
Grade A, and why
oss-strategy 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 8d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open Source Strategy
Guide open source as a commercialization path: build community and trust first, monetize later. Many products use open source for early growth (Supabase, Plausible, Cal.com, Llama, Qwen, Dify) and later commercialize via managed services or open core.
Core insight: Brand is the moat when code is commoditized. Developers won't pay directly; they become your marketing force through word-of-mouth, content, and recommendations.
When to use
- User wants open source strategy, OSS commercialization, or open core / COSS business model.
- Deciding between open core, managed service, or support-first monetization.
- Planning open source growth: community building, stars strategy, DevHunt launch.
- User says "open source strategy", "open source to paid", "open source business model", "OSS 策略", "DevHunt", "开源策略", or "开源商业模式".
Not for: GitHub README/topics/About beautification — that's oss-polish.
Steps
-
Choose the business model. Match the model to the product and audience:
Model Description Examples Open Core Core free; enterprise features (SSO, audit, multi-tenancy) paid GitLab, Elastic, Grafana Managed Services (SaaS) Self-host free; cloud/hosted paid MongoDB Atlas, Confluent, Dify Support-First Free software; enterprise support subscriptions Red Hat Free + Paid Convenience 70–80% revenue from cloud; self-host free Most COSS companies Enterprise users buy risk mitigation — SLAs, indemnification, security patches, support — not just code. For general pricing models, value-based pricing, GTM motions, and the indie-developer revenue ladder beyond OSS — load
references/commercialization-models.md. -
Pick the license. This determines who can fork and whether cloud giants can exploit your work without contributing:
License Use Trade-off MIT, Apache 2.0 Permissive; max adoption Cloud giants can fork without contributing AGPL Prevent cloud fork without contribution May reduce adoption BSL/SSPL Source-available; commercial restrictions Elastic, HashiCorp, Redis Labs shifted to this
What ships with it
2 files 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.
- 8d ago First seen · 80 lines · 67 tokens per session scan A 490990017ed7
oss-strategy is a skill published in the GitHub repository int2t05/engineering-skills (3 stars, last pushed 7d ago), licensed MIT. It adds 67 tokens to every session and 1,102 once invoked, about $0.0003 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
pr-workflow
Crear pull requests completas con descripcion, labels y reviewers.
meta-prompting
Enhanced reasoning patterns via slash commands (/think, /verify, /adversarial, /edge, /compare, /confidence, /budget, /constrain, /json, /flip, /assumptions, /tensions, /analyze, /trade) or natural language ("argue against", "what could break", "show reasoning", "deep review", "meta-prompts", "thinking modes"…
review-prompt
Review LLM prompts against the prompt-engineering skill's principles — leading with where each line came from — and report the findings without modifying files. Use when reviewing prompt quality, auditing a prompt, evaluating a system prompt, or checking whether prompt issues are high-confidence and fixable.
goal-test
A local experiment for testing a goal command that keeps an AI coding session working until a stated condition is judged complete. It uses a separate language model to evaluate the conversation after each assistant turn.
llm
AI features you ship to users: structured output, tool schemas, prompt injection, evals. Use when "the model returns bad JSON", "it hallucinates", "stop it calling the wrong tool", "add evals", or an LLM feature can trigger refunds, emails or writes. Covers schema-constrained output, idempotent tool calls…
fec-drawio-studio
An editable workflow for making technical diagrams in draw.io (also called diagrams.net), with the original .drawio file saved alongside exported images or documents. It covers architecture, database, UML, sequence, flow, machine-learning, and code-structure diagrams.