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 ololand-ai/ololand-plugins --skill firm-playbookgit clone --depth 1 https://github.com/ololand-ai/ololand-pluginsWrote 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/ololand-ai/ololand-plugins/firm-playbook)<a href="https://agentmods.dev/skills/ololand-ai/ololand-plugins/firm-playbook"><img src="https://agentmods.dev/badge/skills/ololand-ai/ololand-plugins/firm-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/ololand-ai/ololand-plugins/firm-playbook"><img src="https://agentmods.dev/badge/skills/ololand-ai/ololand-plugins/firm-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.00086 | $0.00641 |
| Opus 5 | $0.00043 | $0.00320 |
| Sonnet 5 | $0.00017 | $0.00128 |
| Haiku 4.5 | $0.00009 | $0.00064 |
Grade A, and why
ololand-dd-firm-playbook-recall 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 6d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Firm playbook recall
For deals on OloLand, the firm's standing playbook encodes the institution's codified preferences: WACC range, target IRR, min MOIC, EV-multiple ceilings, approval thresholds, standard timelines, preferred frameworks, and custom rules (e.g. "flag top-customer concentration > 30%"). When answering deal questions that produce a number under the firm's name, honor the playbook OR explicitly call out the deviation.
When to call
Call mcp__ololand__recall_firm_playbook(deal_id) at the start of any substantive turn that will:
- Quote a WACC, terminal growth rate, exit multiple, target IRR, or MOIC
- Compare a deal to a target/criteria threshold (revenue size, growth rate, EBITDA margin)
- Recommend an approval routing (partner / IC / board)
- Apply a custom rule (concentration, leverage, segment exposure)
Skip the call for trivial Q&A (greetings, identity, single-fact lookups) where no number is being committed.
Distinct from playbook-recall
| Tool | Scope | Returns |
|---|---|---|
mcp__ololand__recall_firm_playbook |
THIS firm's standing config | WACC ranges, IRR targets, approval thresholds, rules |
mcp__ololand__find_similar_deals (via /playbook-recall) |
Patterns from past similar deals | What worked / what didn't / what got missed |
Both can be load-bearing — the first sets the constraint, the second informs how to apply it.
Deviation discipline
When a playbook value constrains a number you're about to commit to:
- In range — proceed; cite the playbook value as the basis.
- Out of range, justified — quote the playbook value, explain why the deviation is warranted, recommend partner sign-off via
/partner-signoffif the artifact is IC-bound. - Out of range, unjustified — adjust the number to fit the playbook range OR refuse to commit and ask the user to confirm the deviation.
Silent substitution of OloLand defaults when a playbook is configured is a discipline failure — the analyst loses the audit trail and the firm loses the confidence signal.
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.
- 6d ago First seen · 43 lines · 86 tokens per session scan A eff460b7a0ac
ololand-dd-firm-playbook-recall is a skill published in the GitHub repository ololand-ai/ololand-plugins (0 stars, last pushed 5d ago), licensed Apache-2.0. It adds 86 tokens to every session and 641 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
sector-rotation
An analysis framework for comparing industries in the Chinese A-share stock market, using business conditions, price momentum, valuation, and money flows. It produces rankings and higher- or lower-allocation suggestions.
strategy-pivot-designer
Detect backtest iteration stagnation and generate structurally different strategy pivot proposals when parameter tuning reaches a local optimum.
twitter-reader
Read Twitter/X for financial research using opencli (read-only). Use this skill whenever the user wants to read their Twitter feed, search for financial tweets, view bookmarks, look up user profiles, or gather market sentiment from Twitter/X. Triggers include: "check my feed", "search Twitter for", "show my…
chenhao-limit-up
A framework for judging Chinese A-share stocks that have reached the daily price-rise limit, using market mood, sector leadership, and trading momentum.
trading-risk-gate
Unified pre-trade safety gate: Ruin check (Law #1), ergodicity audit, and win-rate dominance validation. Absorbs: ergodicity-check, law-of-ruin, win-rate-dominance.
vectorbt
High-performance vectorized backtesting with parameter optimization, portfolio simulation, and rich performance metrics.