What is ic-approve-readiness?

A pre-approval check for an OloLand investment-committee package, looking for unresolved assumptions and assumptions without supporting evidence.

Use it before approving a deal package to inspect assumption status, evidence quality, and whether a current package exists.

It shows which issues block approval and which evidence is weak but not blocking, so analysts know what must be fixed or reviewed first.

ic-approve-readiness — Command for Claude Code by ololand-ai

Install

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.

Clone the repo

git clone --depth 1 https://github.com/ololand-ai/ololand-plugins

Made for: Claude Code.

Or install ololand-dd, the plugin that ships this one along with the rest of its 22 skills, 52 commands, 3 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/ic-approve-readiness/github.svg)](https://agentmods.dev/commands/ololand-ai/ololand-plugins/ic-approve-readiness)

Your own site

<a href="https://agentmods.dev/commands/ololand-ai/ololand-plugins/ic-approve-readiness"><img src="https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/ic-approve-readiness/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/ololand-ai/ololand-plugins/ic-approve-readiness"><img src="https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/ic-approve-readiness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 965 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00037	$0.00965
Opus 5	$0.00018	$0.00483
Sonnet 5	$0.00007	$0.00193
Haiku 4.5	$0.00004	$0.00097

Measured 8d ago against content hash 1f52817821b9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

ic-approve-readiness 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.

plugins/ololand-dd/commands/ic-approve-readiness.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

IC Approve Readiness

IC package approval is gated by two independent blocker tiers:

Open blocking assumptions — high or critical tracked assumptions still in an unresolved state.
Unsupported high-priority assumptions — high or critical tracked assumptions whose evidence_strength is none (no provenance attached at all).

A separate weak-evidence warning surface flags high/critical assumptions whose evidence_strength is weak or partial. These do NOT block approval, but the IC viewer surfaces them so the analyst knows what to defend.

This command runs the pre-flight check before the analyst attempts to approve.

Usage

/ic-approve-readiness <deal_id>

Arguments

deal_id (required) — The deal whose IC package readiness to assess.

Execution

Call get_assumption_control_summary with the deal_id.
Call get_assumption_evidence_pack to retrieve quality_flags for the deal.
Call get_ic_package(deal_id) to retrieve the latest IC package and its approval_evidence_snapshot. If the response has package: null, no IC package exists yet — note this and continue with just the assumption-level analysis.
Categorize:
- Tier-1 blockers (resolution required): from control_summary.blocking_assumptions — high/critical, status not in {verified, mitigated, invalidated, accepted}.
- Tier-2 blockers (provenance required): from quality_flags — high/critical tracked assumptions with evidence_strength == "none".
- Warnings (review recommended, not blocking): from quality_flags — high/critical tracked assumptions with evidence_strength in {weak, partial}. Cross-reference these against approval_evidence_snapshot.warnings if a package exists.
Render:
- Overall readiness: READY / BLOCKED
- Tier-1 blockers (one row per blocker): assumption_id, statement, status, priority, recommended resolution
- Tier-2 blockers (unsupported high-priority): assumption_id, statement, missing_links, recommended source to attach
- Warnings (weak/partial evidence): assumption_id, statement, evidence_strength, why this is weak, what to add to strengthen it
- Counts: total, open, blocking, by evidence_strength
- Package state (if a package exists): version, status, approved_at, and approval_evidence_snapshot.summary — the snapshot that was captured at the last approval attempt or will be captured next.

Read the full file on GitHub · 66 lines

Changes

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 · 66 lines · 37 tokens per session scan A 1f52817821b9

Subscribe to this mod's changes

ic-approve-readiness is a command published in the GitHub repository ololand-ai/ololand-plugins (0 stars, last pushed 4d ago), licensed Apache-2.0. It adds 37 tokens to every session and 965 once invoked, about $0.0002 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.

Finance and fintech

valuation-methods

Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.

agentii-ai/agentii-investment-intelligence · 17 tokens

merit-reconcile

Preview or check the status of Stripe → Merit payout reconciliation (read-only).

Elnora-AI/elnora-merit-aktiva · 20 tokens

audit-checklist

Perform an internal audit, review controls, or prepare for an external financial audit.

GAJETOso/financeskills · 15 tokens

scan

Scan AWS account for cost optimization.

prajapatimehul/claude-aws-cost-saver · 6 tokens

finops-status

Orientation — say where an opportunity or assignment sits in the five-step FinOps lifecycle and what unlocks next. Useful when a record has no active stage: an opportunity while its assignments do the work, an assignment whose plan has not been approved yet, or a rejected or archived assignment. Read-only; mutates…

glassity/agent-skills · 64 tokens

audit

Scan for non-kernel money math. Rebuild critical flows as JournalEntrys. Replay and prove. Complements /ledger-verify.

eternal-roman/ledger · 0 tokens