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.
npx agentmods add skills/robinsadeghpour/content-workflow/reviewnpx skills add robinsadeghpour/content-workflow --skill reviewgit clone --depth 1 https://github.com/robinsadeghpour/content-workflowWrote 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/robinsadeghpour/content-workflow/review)<a href="https://agentmods.dev/skills/robinsadeghpour/content-workflow/review"><img src="https://agentmods.dev/badge/skills/robinsadeghpour/content-workflow/review.svg" alt="Measured on agentmods" 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.00079 | $0.01852 |
| Opus 5 | $0.00039 | $0.00926 |
| Sonnet 5 | $0.00016 | $0.00370 |
| Haiku 4.5 | $0.00008 | $0.00185 |
Grade A, and why
review 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 5d 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review -- Morning Batch Content Review
Interactive morning review workflow for KEEP/SKIP/STAR decisions on discovered content ideas. One focused pass through the backlog, ~5 minutes, then hand off to content generation.
Workflow
When /review is invoked, execute the following steps in order.
Step 1: Check for today's review file
Run:
cat data/review/$(date +%Y-%m-%d).md 2>/dev/null
If the file exists, display a brief summary to Robin:
"Today's pulse found {N} ideas. Here's the overview:"
Then show the file content (or a condensed version with titles and sources).
If no file exists, tell Robin:
"No pulse has run today. Run /pulse first, or I can review ideas from previous days."
Continue to Step 2 regardless — there may be pending ideas in the DB from earlier pulse runs.
Step 2: Query pending ideas from the database
Run:
node -e "
const db = require('better-sqlite3')('data/content.db');
const ideas = db.prepare(\"SELECT id, title, summary, source_url, source_type, score, status, transcript FROM ideas WHERE status IN ('new', 'starred') ORDER BY score DESC\").all();
console.log(JSON.stringify(ideas));
db.close();
"
Parse the JSON output. If the array is empty, tell Robin:
"No pending ideas to review. All caught up! Run /pulse to discover new ideas."
Stop here if nothing to review.
Step 3: Present ideas and collect decisions
Initialize counters: kept=0, skipped=0, starred=0, remaining=total_count.
For each idea (iterate in order, score DESC):
Display this format:
--- Idea {N}/{total} ---
{title}
Source: {source_type} | {source_url}
Angle: {content_angle_suggestion}
> {summary}
[Transcript available: yes/no]
Content angle suggestion logic (evaluate in order, first match wins):
source_type === 'changelog'→ "News reaction"- title contains (case-insensitive) "tutorial", "how to", "guide", or "learn" → "Tutorial breakdown"
- title contains (case-insensitive) "wrong", "actually", "unpopular", "hot take", or "controversial" → "Hot take"
- title contains (case-insensitive) "vs", "compare", "comparison", or "better" → "Comparison"
- default → "Topic breakdown"
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.
- 5d ago First seen · 218 lines · 79 tokens per session scan A b4b8f35b0a18
review is a skill published in the GitHub repository robinsadeghpour/content-workflow (55 stars, last pushed 3mo ago), licensed MIT. It adds 79 tokens to every session and 1,852 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…