Borrowing it
Nothing to install: this file belongs to markmhendrickson/foundation. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/markmhendrickson/foundation/main/.cursor/skills/publish-plan/SKILL.mdgit clone --depth 1 https://github.com/markmhendrickson/foundationWrote 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/markmhendrickson/foundation/publish-plan)<a href="https://agentmods.dev/skills/markmhendrickson/foundation/publish-plan"><img src="https://agentmods.dev/badge/skills/markmhendrickson/foundation/publish-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/markmhendrickson/foundation/publish-plan"><img src="https://agentmods.dev/badge/skills/markmhendrickson/foundation/publish-plan.svg" alt="Reviewed on agentmods" width="80" 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.00017 | $0.01460 |
| Opus 5.5 | $0.00007 | $0.00584 |
| Sonnet 5.5 | $0.00003 | $0.00292 |
| Haiku 4.5 | $0.00002 | $0.00146 |
Grade A, and why
publish-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 1mo 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.
This is a copy
94% identical to publish-plan — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
publish-plan
Convert a plan file (release plan, feature spec, or .cursor/plans/ file) into a
GitHub Discussion post written for external readers. Strips internal references and
PII, rewrites for a public audience, and optionally posts via the GitHub CLI.
When to Use
Use when you have a plan in progress and want external input before execution. Pass the path to any plan document as the argument:
/publish-plan docs/releases/in_progress/v0.12.0/release_plan.md
/publish-plan .cursor/plans/some_plan.md
/publish-plan docs/feature_units/in_progress/FU-2026-01-001/FU-2026-01-001_spec.md
Optionally pass a specific question to ask readers as a second argument:
/publish-plan docs/releases/in_progress/v0.12.0/release_plan.md "Does this sync model work for your use case?"
Step 1: Read and Parse the Plan
- Read the plan file at the provided path.
- Extract the following from the document:
- Goal / motivation: Why does this exist? What problem does it solve?
- Approach / key decisions: What choices were made or are still open?
- Scope boundaries: What is explicitly excluded or deferred?
- Open questions: What is uncertain or unresolved?
Step 2: Strip Internal References
Remove or redact anything that should not be public:
- Full names and email addresses of individuals
- Internal Slack channels, ticket numbers, or system identifiers that leak org structure
- Pricing, cost, or revenue figures
- Internal hostnames, credentials, or environment-specific configuration values
- Agent execution notes (batch status, orchestrator output, FU dependency trees)
- Anything marked
<!-- internal -->or[INTERNAL]
Do not strip:
- Feature IDs (FU-YYYY-MM-NNN) — these are useful public references
- Architecture decisions and technical rationale
- Version numbers and release IDs
- Links to public repo files or issues
Step 3: Draft the Discussion Post
Rewrite the extracted content into the following structure. Write in plain prose for an external developer audience. No jargon specific to the foundation framework.
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.
- 1mo ago First seen · 212 lines · 17 tokens per session scan A fccca9e7443a
publish-plan is a skill published in the GitHub repository markmhendrickson/foundation (2 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 1,460 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to publish-plan, differing in 7 lines, and is treated as a copy.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.