Open Mercato is an open-source TypeScript foundation framework for building CRM, ERP, commerce, and other business applications with established architecture, specifications, permissions, events, and domain modules. It is for teams and developers who want AI coding assistants to build consistent business software on top of ready-made foundations. The catalogue add-ons teach agents the framework’s conventions and workflows for implementing, testing, reviewing, and debugging features.
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 open-mercato/open-mercato --skill stage-playbookgit clone --depth 1 https://github.com/open-mercato/open-mercatoWrote 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/open-mercato/open-mercato/stage-playbook)<a href="https://agentmods.dev/skills/open-mercato/open-mercato/stage-playbook"><img src="https://agentmods.dev/badge/skills/open-mercato/open-mercato/stage-playbook/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/open-mercato/open-mercato/stage-playbook"><img src="https://agentmods.dev/badge/skills/open-mercato/open-mercato/stage-playbook.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.00021 | $0.00250 |
| Opus 5.5 | $0.00008 | $0.00100 |
| Sonnet 5.5 | $0.00004 | $0.00050 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
stage-playbook 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
92% identical to stage_playbook — 6 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.
What it actually says
Use this playbook to pick the single most appropriate next stage for a deal.
Pipeline stages, in order:
lead— initial interest, no qualification yet.qualified— budget, authority, need, and timeline (BANT) confirmed.proposal— a quote or proposal has been sent.negotiation— terms are actively being discussed.won— the deal is closed and signed.lost— the deal is dead; record the reason.
Decision rules:
- Advance one stage at a time unless a strong signal justifies a jump.
- Strong forward signals: a signed document, a scheduled close date, an explicit verbal commitment, or procurement engagement.
- Risk signals that hold a deal back: no reply for two or more weeks, the champion leaving, or repeated reschedules.
- When momentum is unclear, prefer the conservative stage and lower your confidence rather than guessing high.
Always justify the chosen stage in the rationale with the specific signal you relied on.
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 · 28 lines · 21 tokens per session scan A 7fb99c100e55
stage-playbook is a skill published in the GitHub repository open-mercato/open-mercato (1,865 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 250 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to stage_playbook, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
typescript-idioms
TypeScript strict typing: type narrowing, discriminated unions, Zod runtime validation, generic utility types, and Vitest testing. Use when writing or refactoring TypeScript across frontend, backend, or full-stack projects.
hono-idioms
Hono lightweight web framework patterns: type-safe route handlers, middleware composition, Zod validation, and RPC clients for Cloudflare Workers, Node, or Bun. Use when building Hono APIs. Pair with typescript-idioms.
typescript-expert
TypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling.
investigate
Investigate a specific issue report with strict, evidence-driven diagnosis.
orchestrate
Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses listtasks, listactivetasksbyorg, listmembers, updatetask, getworkunitprogress.
ticket-craft
Create Jira/Asana/Linear tickets optimized for Claude Code execution - AI-native ticket writing.