approve

approve is a skill for Claude Code from robinsadeghpour/content-workflow. It costs 62 tokens per session (1,079 once invoked), scanned A, original, MIT.

An approval and scheduling workflow for social-media drafts. It shows reviewed text for TikTok, Instagram, and LinkedIn so a person can approve, reject, edit, or schedule it through Postiz, a publishing tool.

In plain words
What is it for?
Use it to review pending posts, filter them by platform, edit or reject drafts, approve them, and schedule or publish them.
Why use it?
It keeps a human decision between draft creation and publication, and gathers pending drafts in one review process.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: names the AskUserQuestion tool.

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/robinsadeghpour/content-workflow/approve
Any agent
npx skills add robinsadeghpour/content-workflow --skill approve
Clone the repo
git clone --depth 1 https://github.com/robinsadeghpour/content-workflow

Made for: Claude Code.

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 approve

README.md
[![agentmods](https://agentmods.dev/badge/skills/robinsadeghpour/content-workflow/approve.svg)](https://agentmods.dev/skills/robinsadeghpour/content-workflow/approve)
Your own site
<a href="https://agentmods.dev/skills/robinsadeghpour/content-workflow/approve"><img src="https://agentmods.dev/badge/skills/robinsadeghpour/content-workflow/approve.svg" alt="Measured on agentmods" 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 1,079 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00062 $0.01079
Opus 5 $0.00031 $0.00540
Sonnet 5 $0.00012 $0.00216
Haiku 4.5 $0.00006 $0.00108

Measured 6d ago against content hash 30abd9e43320, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

approve 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.

.claude/skills/approve/SKILL.md · 126 lines

How it starts

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

/approve — Content Approval & Scheduling

Interactive approval workflow for publishing content through Postiz.

Activation Triggers

  • /approve
  • approve content
  • schedule posts
  • review drafts for publishing
  • publish content

Platform Filter

If Robin specifies a platform, pass it through:

  • /approve linkedin or /approve --linkedin--platform linkedin
  • Same for tiktok_en, tiktok_de, instagram

Workflow

Step 1: Fetch Pending Drafts

cd /Users/robinsadeghpour/content-workflow && node scripts/approve-draft.js --list

If Robin specified a platform filter:

cd /Users/robinsadeghpour/content-workflow && node scripts/approve-draft.js --list --platform <platform>

Parse the JSON array output. If the array is empty, tell Robin:

No drafts pending approval. Run /generate-content first to create drafts.

Step 2: Check for Failed Retries

cd /Users/robinsadeghpour/content-workflow && node scripts/approve-draft.js --list-pending

If any pending-schedule drafts exist, inform Robin and offer to retry them.

Step 3: Present Each Draft for Review

For each draft from --list output, use AskUserQuestion to present:

## [PLATFORM_BADGE] Draft: <draft_id>

**Voice Score:** <voice_score from critic>/10
**Visual:** <visual_approach> (<slide_count> slides)

---

### Voice Pass Diff

**BEFORE (original):**
<original_text from --list output — the pre-humanizer version>

**AFTER (humanized):**
<full final text — the humanized caption or post_text>

---

**Scheduled for:** <default schedule time from config>

→ **Approve** / **Reject** / **Edit** / **Skip**

If original_text is null (draft predates diff tracking), show only the final text with a note: "(Original text not available — draft created before diff tracking was added)"

Display fields:

  • Platform badge: LINKEDIN / TIKTOK_EN / TIKTOK_DE / INSTAGRAM
  • Draft ID: from the list output
  • Voice score: critic's voice authenticity score (from content JSON if present)
  • BEFORE (original): the original_text field from list output — pre-critic version
  • AFTER (humanized): the final humanized content — show caption for tiktok/instagram, post_text for linkedin
  • Visual approach + slide count: if applicable
  • Default schedule time: computed from config/schedule-defaults.json

Read the full file on GitHub · 126 lines

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. 6d ago First seen · 126 lines · 62 tokens per session scan A 30abd9e43320

Subscribe to this mod's changes

approve is a skill published in the GitHub repository robinsadeghpour/content-workflow (55 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 1,079 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

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

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…

microsoft/vscode · 72 tokens