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 skills add Jamie-BitFlight/claude_skills --skill seven-prompt-content-enginegit clone --depth 1 https://github.com/Jamie-BitFlight/claude_skillsWrote 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/jamie-bitflight/claude_skills/seven-prompt-content-engine)<a href="https://agentmods.dev/skills/jamie-bitflight/claude_skills/seven-prompt-content-engine"><img src="https://agentmods.dev/badge/skills/jamie-bitflight/claude_skills/seven-prompt-content-engine/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/jamie-bitflight/claude_skills/seven-prompt-content-engine"><img src="https://agentmods.dev/badge/skills/jamie-bitflight/claude_skills/seven-prompt-content-engine.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Output Handling · line 193 Output size or generation rate is not bounded. Unbounded output enables denial-of-service through resource exhaustion, log flooding, or context-window stuffing.Fix: Set explicit limits on output length, generation count, and rate. Use max_tokens and truncation to prevent unbounded output.
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.00106 | $0.01710 |
| Opus 5 | $0.00053 | $0.00855 |
| Sonnet 5 | $0.00021 | $0.00342 |
| Haiku 4.5 | $0.00011 | $0.00171 |
Grade A, and why
seven-prompt-content-engine 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 8d 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Seven Prompt Content Engine
Purpose
Runs a fixed 7-step sequential pipeline that converts a rough idea into a finished, platform-adapted content asset plus standalone repurposed outputs. Each step consumes the prior step's output. Do not skip steps unless the user explicitly provides the missing upstream material.
When to Use
Invoke this skill when the user wants to:
- Turn a rough thought, frustration, client situation, or lesson into a finished post
- Build a repeatable content system with consistent structure
- Generate hooks, outlines, drafts, and platform variants in one pass
- Reduce blank-page time with a guided process
- Make AI writing sound more human
- Repurpose one piece into many standalone assets
Do not invoke this skill when the user only wants:
- Proofreading or light editing with no process
- Generic brainstorming with multiple broad options returned
- A one-off rewrite with no repeatable framework
Core Operating Rules
- Keep the chain linear — output of each step is the input for the next
- Default to one strong angle in Step 1; never return a menu of broad topics
- Preserve the user's audience, offer, and lived experience whenever known
- Prefer specificity over polish in early steps (Steps 1–3)
- In Step 4, match only voice constraints the user explicitly provides; do not claim perfect voice-matching
- In Step 5, audit for detectable AI patterns, not just grammar
- In Step 6, adapt natively per platform; do not copy-paste the same text across destinations
- In Step 7, extract assets that stand alone without the original piece
- If the user provides a URL to a writing sample or source material, read it before drafting
- Pause after any step if the user asks to revise; otherwise continue through the full chain
Intake
Collect or infer before starting:
| Input | Required | Notes |
|---|---|---|
| Rough idea / frustration / client situation / lesson / observation | Required | Core material for Step 1 |
| Target audience | Required | Shapes angle, voice, platform fit |
| Desired platform or primary destination | Required | Drives Step 6 |
| Offer / business context | Optional | Sharpens angle specificity in Step 1 |
| Writing sample | Optional | Used in Step 4 for voice matching |
| Banned phrases / tone constraints / formatting constraints | Optional | Applied in Steps 4 and 5 |
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.
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.
- 8d ago First seen · 212 lines · 106 tokens per session scan A 48308c71df85
seven-prompt-content-engine is a skill published in the GitHub repository Jamie-BitFlight/claude_skills (66 stars, last pushed today), licensed MIT. It adds 106 tokens to every session and 1,710 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-09-03.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…