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/igptai/skills/strategic-commitment-lognpx skills add igptai/skills --skill strategic-commitment-loggit clone --depth 1 https://github.com/igptai/skillsWrote 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/igptai/skills/strategic-commitment-log)<a href="https://agentmods.dev/skills/igptai/skills/strategic-commitment-log"><img src="https://agentmods.dev/badge/skills/igptai/skills/strategic-commitment-log.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.00099 | $0.01463 |
| Opus 5 | $0.00049 | $0.00732 |
| Sonnet 5 | $0.00020 | $0.00293 |
| Haiku 4.5 | $0.00010 | $0.00146 |
Grade A, and why
strategic-commitment-log 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strategic Commitment Log
Prerequisites
This skill needs the iGPT MCP at https://mcp.igpt.ai/.
If the MCP tools aren't available or return an auth error, tell the
user to install the iGPT plugin (/plugin marketplace add igptai/skills)
or add https://mcp.igpt.ai/ as a connector, then complete OAuth and say
"ready". Retry once after they confirm. Never invent tokens or OAuth URLs.
For deeper troubleshooting: https://raw.githubusercontent.com/igptai/skills/main/shared/mcp-guard.md
What This Skill Does
Scans email threads with investors, board members, key partners, and strategic stakeholders to find every commitment the executive has made — targets promised, milestones committed to, decisions pledged — and tracks which remain open and which have been delivered on.
Workflow
-
Before calling any tool, collect these values from the user. Offer the defaults and let the user override them; do not invent values they did not give.
- [time_range] — what window of email to scan. The user may give this in any form ("last 18 months", "the last year", "May 2024", "since the Series A"). Default: the last 18 months. Keep the user's natural phrasing for use in the ask input; convert to ISO dates separately for the search call.
- [stakeholder_scope] — either "all" (default) or the name of a specific stakeholder to focus on.
- [stakeholder_clause] — derived. When [stakeholder_scope] is not "all", set to " for stakeholder [stakeholder_scope]". When [stakeholder_scope] is "all", set to empty string.
-
Call search with:
- query: commit promise will deliver target milestone by end of quarter we will achieve plan board investor (if [stakeholder_scope] is not "all", append the stakeholder name to the query)
- date_from: ISO start date derived from [time_range]
- date_to: ISO end date derived from [time_range] (or today if open-ended)
-
Call ask with:
- input: Review all email threads from [time_range][stakeholder_clause] involving investors, board members, partners, and strategic stakeholders. Find every commitment, promise, or target the founder or executive made — things like revenue targets committed to, milestones pledged, strategic decisions promised, hires committed to, and formal undertakings made. For each determine whether there is evidence it was delivered or whether it remains open.
- output_format: { "strict": true, "schema": { "type": "object", "description": "Strategic commitment log tracking executive promises to key stakeholders", "additionalProperties": false, "properties": { "as_of": { "type": "string", "description": "ISO8601 date when this log was generated" }, "commitments": { "type": "array", "description": "List of every strategic commitment found in email", "items": { "type": "object", "description": "A single strategic commitment with delivery status", "additionalProperties": false, "properties": { "commitment": { "type": "string", "description": "Clear statement of what was committed to" }, "committed_to": { "type": "string", "description": "Name or role of the stakeholder to whom this commitment was made" }, "stakeholder_type": { "type": "string", "description": "Type of stakeholder this commitment was made to", "enum": [ "investor", "board_member", "partner", "customer", "regulator", "team", "public", "other" ] }, "commitment_type": { "type": "string", "description": "Category of commitment", "enum": [ "financial_target", "product_milestone", "strategic_hire", "partnership_goal", "operational_target", "legal_obligation", "reporting_commitment", "other" ] }, "made_on": { "type": "string", "description": "ISO8601 date this commitment was made" }, "target_date": { "type": "string", "description": "ISO8601 date by which this was committed to be delivered, empty string if open-ended" }, "evidence": { "type": "string", "description": "Quote or paraphrase from email documenting this commitment" }, "status": { "type": "string", "description": "Current delivery status of this commitment", "enum": ["delivered", "on_track", "at_risk", "overdue", "open", "unknown"] }, "risk_if_missed": { "type": "string", "description": "What is at stake if this commitment is not delivered", "enum": ["critical", "high", "medium", "low"] } }, "required": [ "commitment", "committed_to", "stakeholder_type", "commitment_type", "made_on", "target_date", "evidence", "status", "risk_if_missed" ] } }, "overdue_count": { "type": "number", "description": "Number of commitments that are overdue" }, "at_risk_count": { "type": "number", "description": "Number of commitments that are at risk of not being delivered" }, "summary": { "type": "string", "description": "One or two sentence summary of the commitment landscape and most critical open items" } }, "required": [ "as_of", "commitments", "overdue_count", "at_risk_count", "summary" ] } }
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 · 154 lines · 99 tokens per session scan A 5b7d62113e8a
strategic-commitment-log is a skill published in the GitHub repository igptai/skills (16 stars, last pushed 4mo ago), licensed MIT. It adds 99 tokens to every session and 1,463 once invoked, about $0.0005 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
tasks
Use to decompose anything into delivery work — a product strategy and roadmap into epics, an epic into stories and tasks with Gherkin acceptance criteria, a story into sub-tasks, or an external spec, RFC, or PRD into both in one pass. Resolves the work item's source system (Linear, Jira, GitHub/GitLab issues, or…
skill-review
Use when the user wants to research, review, or enhance an agent skill on a regular cadence — weekly skill uplift, audit a SKILL.md against best practice, compare with popular external skills, fix working issues, or align with agentskills.io. Triggers on "review this skill", "enhance the X skill", "weekly skills…
code-review
Use when the user wants a code review of a branch, PR, MR, or working diff against its acceptance criteria and declared scope, in whatever form they take in this repo. Triggers on "review my branch", "review this PR", "check this diff before I raise it", "is this ready to merge". Works with any language, delivery…
ux-design-review
Use when the user wants a UX or design review of implemented UI — components, pages, or flows — against its design source, covering accessibility (WCAG 2.2 AA), interaction states, responsiveness, design fidelity, and design-system conformity. Triggers on "review the checkout page", "check this UI before I ship it"…
docs-review
Use when the user wants a set of documents reviewed — a docs folder, a wiki, a handbook, a repo's markdown, or any collection of written material. Checks that each document is well written and well structured, that boundaries between documents are clear with no duplication, and that the set is consistent and cohesive.…
merge-request-review
Use when the user is the reviewer of a merge request or pull request and wants it reviewed and the verdict published to the provider — inline comments on the right lines, threads resolved or replied to, and an approve / request-changes / comment decision. Handles first reviews and re-review rounds after the author…