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 martineserios/thebrana --skill supply-demand-balancegit clone --depth 1 https://github.com/martineserios/thebranaWrote 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/martineserios/thebrana/supply-demand-balance)<a href="https://agentmods.dev/skills/martineserios/thebrana/supply-demand-balance"><img src="https://agentmods.dev/badge/skills/martineserios/thebrana/supply-demand-balance/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/martineserios/thebrana/supply-demand-balance"><img src="https://agentmods.dev/badge/skills/martineserios/thebrana/supply-demand-balance.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.00033 | $0.01677 |
| Opus 5.5 | $0.00013 | $0.00671 |
| Sonnet 5.5 | $0.00007 | $0.00335 |
| Haiku 4.5 | $0.00003 | $0.00168 |
Grade A, and why
supply-demand-balance 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 1mo 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.
This is a copy
100% identical to supply-demand-balance — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supply Demand Balance
Master marketplace liquidity by identifying bottlenecks and strategically scaling the harder side of the market.
Help the user with supply demand balance using insights from 6 guests and posts across Lenny's Podcast and Newsletter.
How to Help
- Diagnose constraints - Analyze transaction data to determine if supply or demand is the primary factor limiting your current growth.
- Select acquisition levers - Evaluate and prioritize the top two or three channels most likely to successfully bootstrap your initial supply side.
- Define density targets - Establish clear thresholds for supply variety and volume needed to keep the demand side engaged.
- Resolve trade-offs - Use guiding principles to navigate conflict between supply and demand needs during product prioritization.
Core Principles
Concentrate resources on supply first
From "How to Kickstart and Scale a Marketplace Business – Part 2: Cracking the Chicken-and-Egg Problem 🐣 - Supply vs. Demand": "The lesson we took away from this was that all that matters is supply. So we decided to focus on that above all else. We postponed building brand and delightful product until we had liquidity. Dozens of other startups took another direction. Case after case, it proved a mistake."
Achieve early liquidity by focusing nearly all resources on growing supply before investing heavily in brand building or product polish.
Pinpoint the primary bottleneck
From "How To Know If You're Supply or Demand Constrained 🤹♂️ - Phase 2 of Kickstarting and Scaling a Marketplace Business": "It simply means that your biggest constraint to driving additional transactions is a lack of supply (e.g. Airbnb Homes, Uber drivers) or a lack of demand (e.g. Rover dog owners, TaskRabbit customers). In theory, you always want more of both, but in many cases adding more of one side doesn’t actually lead to growth. Your resources are better spent elsewhere."
Growth depends on identifying which side of the marketplace is currently limiting transactions so you do not waste resources on the side that is already ready.
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.
- 1mo ago First seen · 88 lines · 33 tokens per session scan A 93025a7a55db
supply-demand-balance is a skill published in the GitHub repository martineserios/thebrana (3 stars, last pushed 3d ago), licensed MIT. It adds 33 tokens to every session and 1,677 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to supply-demand-balance, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
pr
Comprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue.
root-cause-investigator
Systematic root cause analysis for errors, bugs, and unexpected behaviors using 5-Why methodology. Use when user reports errors, build failures, test failures, performance issues, integration problems, or any "it's not working" scenarios.
crap-analyzer
Use to produce a risk-based refactor + test plan for recently-changed code on a diff/branch/PR by computing CRAP (complexity × untested) on changed methods. Multi-language — TypeScript, JavaScript, Python, Java, Kotlin, Go, Ruby, C#, Rust, PHP — auto-discovers how the repo generates coverage. Triggers …
init
First-time Archcore setup. Wires the host (MCP config, hooks, CLAUDE.md/AGENTS.md managed block), measures the authored context the repo already holds, then composes a first-day seed — stack rule, run guide, data-model, integrations, config, entry points, public surface, a linked architecture overview, and specs for…
review
Review branch changes against Archcore docs, or report project health. Use for 'review my branch', 'review the changes before merge', 'show status', 'documentation gaps', 'check if docs match code', 'close out the feature', 'ship the feature and close it out', or after a staleness warning. Modes, named as the first…
eu-ai-act-check
Use when checking EU AI Act compliance; redirects to the canonical claude-governance implementation.