Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/zime-ai/zime-gtm-skillsnpx agentmods add skills/zime-ai/zime-gtm-skills/mutual-action-planWrote 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/zime-ai/zime-gtm-skills/mutual-action-plan)<a href="https://agentmods.dev/skills/zime-ai/zime-gtm-skills/mutual-action-plan"><img src="https://agentmods.dev/badge/skills/zime-ai/zime-gtm-skills/mutual-action-plan/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.
<a href="https://agentmods.dev/skills/zime-ai/zime-gtm-skills/mutual-action-plan"><img src="https://agentmods.dev/badge/skills/zime-ai/zime-gtm-skills/mutual-action-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00085 | $0.01252 |
| Opus 5 | $0.00043 | $0.00626 |
| Sonnet 5 | $0.00017 | $0.00250 |
| Haiku 4.5 | $0.00009 | $0.00125 |
Grade A, and why
mutual-action-plan 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 12d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mutual Action Plan
You are a deal-intelligence writer. Write a mutual action plan out of what
was actually said on a call: milestones from today to signature, each with
an owner on both sides and a date. This is a phase-2 deal-intelligence
skill — it writes something forward, it does not grade the call against a
rubric the way next-step-commitment or meddicc do.
Before you start
- If
.agents/gtm-context.md(or.claude/gtm-context.md) exists, read it first and don't ask for anything it already answers. - Run this end to end without stopping to ask which milestones to include —
apply the
heard/inferredtest below to everything the call surfaced and report the result, including an all-inferred plan if that's what the call actually supports. - Don't invent a milestone the call never gestured toward, even to fill out a plan that looks sparse.
When to use this
- A rep just got off a call that covered next steps and wants a MAP to send the prospect, not a to-do list they invented themselves afterward.
- A manager wants to check whether a deal's "next steps" actually hang together as milestones, or are one-sided promises dressed up as a plan.
- RevOps wants to fill gaps in a deal's stage/date fields from what a call actually established, without overwriting what the CRM already has right.
What makes a milestone real
Same three-part test next-step-commitment uses for a single commitment,
applied to every milestone in the plan:
- A specific action — not "follow up," a named thing (a security review completed, a contract sent for signature, budget approved).
- A date or concrete trigger — a calendar date or an event with an obvious, checkable occurrence, not "soon."
- Two-sided ownership — someone on the account owns it too, not just the rep.
See references/rubric.md for the full test and how it maps to the
heard / inferred tags below.
The evidence rule
Every milestone is tagged:
heard— the milestone, its date, and its owners were actually said on the call; quote it.inferred— the milestone is a reasonable next step given what was discussed, but wasn't stated with enough of the three-part test present — the closest thing said is a hand-wave. Quote the closest thing said, and name which of the three elements is missing or assumed.
What ships with it
3 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.
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.
- 12d ago First seen · 127 lines · 85 tokens per session scan A aca6f4a5e80d
mutual-action-plan is a skill published in the GitHub repository zime-ai/zime-gtm-skills (14 stars, last pushed 17d ago), licensed MIT. It adds 85 tokens to every session and 1,252 once invoked, about $0.0004 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
go-to-market-playbook
A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.
category-point-of-view
Create a differentiated B2B category point of view that leads with the customer problem, defines the market shift, names the category or strategic frame, and turns it into content, distribution, and measurement guidance.
b2b-pmm-orchestrator
Route vague B2B product marketing requests to the right PMM skill, sequence multiple skills into intelligent GTM workflows, and keep the agent focused on the smallest useful artifact that moves the business forward.
ai-pmm-reviewer
Review AI-generated B2B marketing and PMM drafts for strategic sharpness, customer truth, positioning quality, plain English, and AI tells; diagnose gaps and rewrite only where judgment is clear.
customer-story-engine
Capture true customer stories and turn them into plain-spoken B2B story assets: story briefs, case studies, one-page PDFs, website posts, and sales proof.
demo-storyline
Create a buyer-centered B2B SaaS demo storyline that maps product moments to buyer pain, uses realistic data, prompts discovery throughout, and ends with a clear recap and next step.