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 cim-generationgit 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/cim-generation)<a href="https://agentmods.dev/skills/ololand-ai/ololand-plugins/cim-generation"><img src="https://agentmods.dev/badge/skills/ololand-ai/ololand-plugins/cim-generation.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.00057 | $0.00479 |
| Opus 5 | $0.00028 | $0.00239 |
| Sonnet 5 | $0.00011 | $0.00096 |
| Haiku 4.5 | $0.00006 | $0.00048 |
Grade A, and why
cim-generation 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.
What it actually says
CIM Generation Skill
When the user asks for a CIM or sell-side marketing document for a deal, use the deterministic OloLand generator rather than drafting the document yourself from context. The platform assembles sections from reconciled financial snapshots, risk/opportunity insights, and market research so every exhibit is traceable — writing one from scratch in-context would lose that provenance.
Trigger phrases
- "generate a CIM" / "create a CIM" / "draft a CIM" / "prepare a CIM"
- "confidential information memorandum"
- "seller memorandum" / "sell-side memo"
- "information package" / "offering memorandum"
- "marketing document for the target"
- "CIM for this deal"
Execution
- Identify the
deal_idfrom the conversation context (current deal, recent mentions, or ask the user). - Follow
/cim-generate(this plugin's command): callgenerate_cim(deal_id), pollcheck_task_status(task_id)every ~5 seconds up to ~24 attempts (~2 minutes), then reportcim_id, section count, and the deal workspace link where the user can view, edit, and export the finished document. If the task is still pending when the polling budget runs out, stop polling — tell the user generation continues server-side, give them thetask_idto re-check later, and note the finished CIM will appear in the deal workspace regardless. - If the user only wants specific sections, first map each user-phrased name to its exact snake_case identifier from the command's 14-section list (e.g. "Executive Summary" →
executive_summary, "risk section" →risk_factors), then pass those identifiers as thesectionsargument rather than generating all 14. Confirm with the user when a phrase is ambiguous. - Do not write CIM content directly in the conversation — the tool call is the source of truth, and the finished document lives on the deal, not in chat history.
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 · 25 lines · 57 tokens per session scan A 8dafc79192e0
cim-generation is a skill published in the GitHub repository ololand-ai/ololand-plugins (0 stars, last pushed 3d ago), licensed Apache-2.0. It adds 57 tokens to every session and 479 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
dcf-model
Build discounted cash flow valuation workbooks in Excel.
comps-analysis
Build comparable-company valuation workbooks in Excel.
excel-author
Build auditable financial workbooks headless via openpyxl.
lbo-model
This skill should be used when completing LBO (Leveraged Buyout) model templates in Excel for private equity transactions, deal materials, or investment committee presentations. The skill fills in formulas, validates calculations, and ensures professional formatting standards that adapt to any template structure.
pitch-deck
Populates investment banking pitch deck templates with data from source files. Use when: user provides a PowerPoint template to fill in, user has source data (Excel/CSV) to populate into slides, user mentions populating or filling a pitch deck template, or user needs to transfer data into existing slide layouts. Not…
audit-xls
Audit a spreadsheet for formula accuracy, errors, and common mistakes. Scopes to a selected range, a single sheet, or the entire model (including financial-model integrity checks like BS balance, cash tie-out, and logic sanity). Triggers on "audit this sheet", "check my formulas", "find formula errors", "QA this…