What is substack-draft-status?

A read-only checker that compares Substack drafts with matching local workspaces containing post files and rendered images. Substack is a publishing service for newsletters and posts.

Use it to check whether drafts were saved, find unmatched local or server drafts, and spot local drafts that may be stale.

It shows whether a draft exists only locally, only on Substack, or in both places, reducing uncertainty about unsent work.

substack-draft-status — Skill by mphinance

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.

agentmods

npx agentmods add skills/mphinance/alpha-skills/substack-draft-status

Any agent

npx skills add mphinance/alpha-skills --skill substack-draft-status

Clone the repo

git clone --depth 1 https://github.com/mphinance/alpha-skills

Made for: Claude Code, Codex.

Per session 103 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 771 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00103	$0.00771
Opus 5	$0.00051	$0.00385
Sonnet 5	$0.00021	$0.00154
Haiku 4.5	$0.00010	$0.00077

Measured 2d ago against content hash ff02ccc93cc5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

substack-draft-status 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 2d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/status.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/mph-kit/skills/substack-draft-status/SKILL.md · 49 lines

How it starts

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

Substack Draft Status

Reconciles two sources of "what drafts do I have":

Local workspaces under ~/.mph-substack-cache/<slug>/ (rendered images + post.md)
Server drafts at https://mphinance.substack.com/api/v1/drafts

The "did I save that yesterday" anxiety usually means: a local workspace exists but it never got pushed. This skill makes that visible in 5 seconds.

When to invoke

User asks "did I save that draft" / "is that on substack" / "what drafts do I have"
User mentions a recent post by date or topic and wants to confirm its state
Before forging a new substack post, sanity-check that an older one isn't sitting half-pushed

Flow

Run the worker:

python ~/.claude/skills/substack-draft-status/scripts/status.py

The script reads SUBSTACK_SID from C:\Users\mphan\OneDrive\Documents\GitHub\mphinance\secrets.env (or the SUBSTACK_SID env var) and hits GET /api/v1/drafts?limit=20.
It walks ~/.mph-substack-cache/ and matches each workspace against server drafts by date-prefix and title.
Output is grouped:
- Pushed — local workspace AND matching server draft (shows edit URL)
- Server-only — draft on substack with no local workspace (created via web)
- Local-only fresh — workspace exists, no server match, post.md mtime within 3 days
- Local-only STALE — workspace exists, no server match, post.md mtime older than 3 days. These are the "forgotten" drafts.
Surface the table verbatim to the user. If any STALE entries exist, offer to push them via mph-substack-publish (do not push automatically).

Hard rules

Read-only. Never call POST /api/v1/drafts/.../publish. Never modify local workspaces. Publishing is mph-substack-publish's job and requires explicit confirmation there.
Reuse the existing secrets.env auth pattern from create_draft_from_md.py. Do not invent a new auth flow.
Do not commit ~/.mph-substack-cache/ contents to git. Those workspaces are local-only by user policy.
If SUBSTACK_SID is missing, print a clear error pointing at secrets.env and exit 2. Do not try to interactively prompt for credentials.
Stale threshold = 3 days. If user wants a different threshold, pass --stale-days N.

Read the full file on GitHub · 49 lines

Files

What ships with it

1 file 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.

scripts/status.py 10 KB runs code

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.

2d ago First seen · 49 lines · 103 tokens per session scan A ff02ccc93cc5

Subscribe to this mod's changes

substack-draft-status is a skill published in the GitHub repository mphinance/alpha-skills (19 stars, last pushed 4d ago), licensed MIT. It adds 103 tokens to every session and 771 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.

Writing and docs

systematic-debugging

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

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens