mutual-action-plan-builder

mutual-action-plan-builder is a skill for Codex from nthnclrk/enablement-skills. It costs 62 tokens per session (926 once invoked), scanned A, original, MIT.

A shared execution plan for a complex deal or customer initiative, with milestones, dates, acceptance criteria, and an owner on both the buyer and seller sides.

In plain words
What is it for?
Use it to coordinate approvals, security reviews, dependencies, stakeholders, and agreed steps toward a target outcome.
Why use it?
It makes responsibilities and commitments visible instead of leaving the seller with an unconfirmed task list.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to coordinate approvals, security reviews, dependencies, stakeholders, and agreed steps toward a target outcome.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nthnclrk/enablement-skills/mutual-action-plan-builder
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.

Any agent
npx skills add nthnclrk/enablement-skills --skill mutual-action-plan-builder
Clone the repo
git clone --depth 1 https://github.com/nthnclrk/enablement-skills

Made for: Codex.

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.

agentmods badge for mutual-action-plan-builder

README.md
[![agentmods](https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/mutual-action-plan-builder/github.svg)](https://agentmods.dev/skills/nthnclrk/enablement-skills/mutual-action-plan-builder)
Your own site
<a href="https://agentmods.dev/skills/nthnclrk/enablement-skills/mutual-action-plan-builder"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/mutual-action-plan-builder/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.

agentmods 80×15 button for mutual-action-plan-builder

Your own site · 80×15
<a href="https://agentmods.dev/skills/nthnclrk/enablement-skills/mutual-action-plan-builder"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/mutual-action-plan-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 926 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00062 $0.00926
Opus 5 $0.00031 $0.00463
Sonnet 5 $0.00012 $0.00185
Haiku 4.5 $0.00006 $0.00093

Measured 11d ago against content hash 3e7c7ac6a143, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

mutual-action-plan-builder 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 11d 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.

skills/mutual-action-plan-builder/SKILL.md · 75 lines

How it starts

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

Mutual action plan builder

Write a plan both sides own. If only sellers have owners, it is a task list.

A MAP is a shared execution plan for a complex deal or coordinated initiative. Every milestone has a buyer-side owner and a seller-side owner. If the user wants proposal or RFP process orchestration, use proposal-rfp-orchestrator.

Two owners. "Security questionnaire submitted — buyer: Priya (InfoSec), seller: Jordan (SE). Exit: filed in their portal. Agreed 22 April, Priya's email."

Task list. "Complete security review. Owner: AE. Due: end of quarter."

Silence is not agreement. A calendar invite is not a commitment.

Confirm Inputs First

Ask only for the inputs that change the plan:

  1. Target outcome and target date, and whether the customer has agreed to them
  2. Current stage, known durations, lead times, blackout dates, and dependencies
  3. Buyer-side and seller-side stakeholders
  4. Required milestones and approvals
  5. Existing confirmations, with source and date

If a customer owner, date, or acceptance criterion is unconfirmed, leave it proposed. Do not invent commitments, logos, pricing, or approval timelines.

Read The Right Reference

Read references/map-framework.md for agreement states, the two-owner test, and infeasible-date handling. Skip it if the user already has a live MAP and only wants a gap pass.

Default Workflow

  1. Anchor the outcome. The concrete result the plan must deliver, and by when. Mark the outcome and date draft, proposed, or agreed. Done when you can say what "done" looks like in customer language.
  2. Reverse-map milestones. Work backward from the target using verified durations, lead times, capacity, and blackouts. Name the critical path, latest-safe-start dates, and slack. If the target cannot be met, say target infeasible — replan required. Do not compress unknown work.
  3. Put two owners on every milestone. Buyer-side and seller-side. A missing buyer owner is a gap, not a seller-owned task. Keep unconfirmed customer owners proposed.
  4. Write entry and exit criteria a third party could inspect. Not "security complete." What artifact, in what system, accepted by whom.
  5. Attach risk only where it changes a date. Signal, mitigation, escalation trigger on the critical path. Internal scoring stays off the customer view.
  6. Check mutuality. Agreement state and completion-evidence state are independent. Attach confirmation source and date. Do not infer agreed from silence, attendance, or a seller CRM note.
  7. Split the views. Shared commitments on the customer-visible MAP. Negotiation strategy, internal risk, and contingency on the internal companion.
  8. Control changes. When an agreed owner, date, milestone, or exit criterion changes, show the prior value and return the field to proposed or changed until the customer reconfirms.

Read the full file on GitHub · 75 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

  1. 11d ago First seen · 75 lines · 62 tokens per session scan A 3e7c7ac6a143

Subscribe to this mod's changes

mutual-action-plan-builder is a skill published in the GitHub repository nthnclrk/enablement-skills (13 stars, last pushed 21d ago), licensed MIT. It adds 62 tokens to every session and 926 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens