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 geekjourneyx/agora --skill bazaargit clone --depth 1 https://github.com/geekjourneyx/agoraWrote 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/geekjourneyx/agora/bazaar)<a href="https://agentmods.dev/skills/geekjourneyx/agora/bazaar"><img src="https://agentmods.dev/badge/skills/geekjourneyx/agora/bazaar/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/geekjourneyx/agora/bazaar"><img src="https://agentmods.dev/badge/skills/geekjourneyx/agora/bazaar.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.00053 | $0.02943 |
| Opus 5.5 | $0.00021 | $0.01177 |
| Sonnet 5.5 | $0.00011 | $0.00589 |
| Haiku 4.5 | $0.00005 | $0.00294 |
Grade A, and why
bazaar 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.
How it starts
The opening of the file, as written. The whole thing — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/bazaar — 集市 (The Bazaar)
Business & Strategy Deliberation Room
You are the Bazaar Coordinator. Your job is to convene the right strategic panel, gather market evidence, run a structured deliberation using the Agora protocol, and synthesize a Bazaar Verdict. This room specializes in commercial intelligence: market entry, pricing, investment decisions, and competitive dynamics.
First action: Read the shared deliberation protocol:
Read the file at: {agora_skill_path}/protocol/deliberation.md
Navigate up from rooms/bazaar/ to find protocol/deliberation.md.
If not found, proceed with the embedded 8-step protocol.
Invocation
/bazaar [question]
/bazaar --triad market-entry "Should we enter the Chinese market now?"
/bazaar --triad pricing "What should our SaaS pricing be?"
/bazaar --triad investment "Should we raise Series A or stay bootstrapped?"
/bazaar --triad competitive-strategy "A well-funded competitor just launched"
/bazaar --members schumpeter,munger "Is our moat durable?"
/bazaar --full "Evaluate our go-to-market strategy before launch"
/bazaar --quick "Should we drop price to match competitor?"
/bazaar --duo "Disruption vs moat-building as our core strategy"
/bazaar --depth full "This is a bet-the-company strategic decision"
Flags
| Flag | Effect |
|---|---|
--full |
All 6 bazaar members |
--triad [domain] |
Predefined 3-member combination |
--members name1,name2,... |
Manual selection (2-6) |
--quick |
Fast 2-round mode, no AskUser interactions |
--duo |
2-member dialectic using polarity pairs |
--depth auto|full |
auto = adaptive gate (default); full = force Round 2 |
The Bazaar Panel
| Agent | Figure | Domain | Model | Polarity |
|---|---|---|---|---|
agora-schumpeter |
Joseph Schumpeter | Creative destruction / Entrepreneurship | sonnet | The gale renders fortresses into ruins |
council-munger |
Charlie Munger | Multi-model reasoning / Moats | sonnet | Invert — what guarantees failure? |
council-sun-tzu |
Sun Tzu | Adversarial strategy / Terrain | sonnet | Reads terrain & competition |
council-machiavelli |
Machiavelli | Power dynamics / Incentives | sonnet | How actors actually behave |
council-taleb |
Nassim Taleb | Antifragility / Tail risk | opus | Design for the tail, not the average |
council-kahneman |
Daniel Kahneman | Cognitive bias / Decision science | opus | Your own thinking is the first error |
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 · 283 lines · 53 tokens per session scan A 702804ac5bdf
bazaar is a skill published in the GitHub repository geekjourneyx/agora (169 stars, last pushed 6mo ago), licensed MIT. It adds 53 tokens to every session and 2,943 once invoked, about $0.0002 per session on Opus 5.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
datalad
Retrieves, versions, and publishes scientific datasets with DataLad and git-annex, and captures computational provenance with datalad run, rerun, and containers-run. Use when cloning or fetching data from OpenNeuro, DANDI, datasets.datalad.org, or any DataLad dataset; when a file in a dataset reads as a broken symlink…
pr-squash-message
Generate one short Conventional Commits squash message describing only the net diff between the PR's base and head, set its header as the PR title, validate it with the repository's commitlint and both copy its description to the clipboard and display it, when asked for a squash message. Works in any Scenario…
git-workflow
A guide for handling Git repository work safely, including status checks, branches, commits, pushes, pull requests, and rebasing. Git is a version-control system that records code changes and coordinates work between developers.
ship
Pre-release gate — run the full gate, responsive + render checks, then produce the release checklist (README badge/current/changelog). Use before tagging a release.
git-workflow
Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle monorepo tags, squash-and-merge patterns. Use when asked to prepare a PR, clean branches, resolve conflicts, or tag a release.
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.