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 agentmods add skills/zoominfo/zoominfo-mcp-plugin/commitment-ledgernpx skills add Zoominfo/zoominfo-mcp-plugin --skill commitment-ledgergit clone --depth 1 https://github.com/Zoominfo/zoominfo-mcp-pluginWrote 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/zoominfo/zoominfo-mcp-plugin/commitment-ledger)<a href="https://agentmods.dev/skills/zoominfo/zoominfo-mcp-plugin/commitment-ledger"><img src="https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/commitment-ledger.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 | $0.00120 | $0.00616 |
| Opus 5 | $0.00060 | $0.00308 |
| Sonnet 5 | $0.00024 | $0.00123 |
| Haiku 4.5 | $0.00012 | $0.00062 |
Grade A, and why
commitment-ledger 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 5d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commitment Ledger
A two-sided accounting of promises across recent conversations: ours, theirs, and what is still open.
Prerequisites
conversation_intelligence requires at least one connected email or meeting source and consumes AI credits. browse_engagements (used to scope or pick engagements) requires an active integration and is free. If no conversation data exists, say so rather than presenting an empty ledger as "no commitments".
Input
Provided via $ARGUMENTS:
- Scope (required) — an account (company ID or name/domain), a contact (contact ID or name + company), or specific calls to review.
- Emphasis (optional) — e.g. "just what they owe us", "anything tied to the contract". Shapes the output.
Workflow
- Resolve scope. Use a ZoomInfo ID directly, or resolve a name via
search_companies/search_contacts. If the user wants specific calls and none are named, present abrowse_engagementsshortlist to pick from before spending credits. - Extract commitments. Run
conversation_intelligencescoped to the account, contact, or chosen engagement. Ask it to list commitments by side (what we said we would do; what they said they would do), with status and the source meeting. Keep CI scoped to one ID per call; it sees only the last few engagements and cannot count or topic-search, so frame this as a recent-commitments ledger, not an exhaustive audit. - Reconcile. Mark each commitment open, done, or unclear based on later conversations. Flag anything overdue or contradicted. Attribute every line to a source meeting; do not list a commitment the conversation does not support.
Output Format
Commitment Ledger — [Account / Contact]
Covers the last few engagements (through [date]). Not a full-history audit.
We owe them
| Commitment | Made on | Status |
|---|
They owe us
| Commitment | Made on | Status |
|---|
Outstanding / overdue — a short list of what most needs chasing, with who owns it.
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.
- 5d ago First seen · 46 lines · 120 tokens per session scan A bf9567a02bf3
commitment-ledger is a skill published in the GitHub repository Zoominfo/zoominfo-mcp-plugin (7 stars, last pushed yesterday), licensed MIT. It adds 120 tokens to every session and 616 once invoked, about $0.0006 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…