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 prrao87/agent-skills --skill blog-scope-refinergit clone --depth 1 https://github.com/prrao87/agent-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/prrao87/agent-skills/blog-scope-refiner)<a href="https://agentmods.dev/skills/prrao87/agent-skills/blog-scope-refiner"><img src="https://agentmods.dev/badge/skills/prrao87/agent-skills/blog-scope-refiner/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/prrao87/agent-skills/blog-scope-refiner"><img src="https://agentmods.dev/badge/skills/prrao87/agent-skills/blog-scope-refiner.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.00091 | $0.01398 |
| Opus 5 | $0.00046 | $0.00699 |
| Sonnet 5 | $0.00018 | $0.00280 |
| Haiku 4.5 | $0.00009 | $0.00140 |
Grade A, and why
blog-scope-refiner 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 11d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blog Scope Refiner
Purpose
Help the user turn a rough blog idea into a sharp, evidence-backed content brief. Prioritize scope discipline, reader value, concrete takeaways, and "show, not tell" proof over generic ideation.
Operating Stance
Act as a rigorous content strategist and technical editor. Collaborate with the user to narrow the post until the reader promise is specific, useful, and demonstrable.
Do not jump straight to titles or outlines. First establish the audience, the problem, the claim, the proof, and the intended reader transformation.
Push back when the idea is too broad, too fluffy, too vendor-centric, or unsupported by evidence. Ask: "What would have to be true for this post to be worth a reader's time?"
Core Workflow
1. Capture the Seed
Extract or ask for:
- Working topic or thesis
- Product, project, technology, or domain involved
- Intended publication context, if known
- Desired reader action after finishing
- Existing artifacts: code, benchmark data, diagrams, customer examples, docs, demos, launch notes, or research
If the user has only a vague topic, generate 2-3 possible angles and ask them to pick or revise one before proceeding.
2. Define the Reader
Identify the ideal reader/customer profile with practical specificity:
- Role and seniority
- Current workflow or pain
- Technical context and constraints
- What they already believe or know
- What they are skeptical about
- What decision they are trying to make
Prefer a narrow reader over a universal one. If multiple reader profiles appear, separate them and ask which one the post must win first.
3. Pin the Reader Promise
Force the post into one primary promise:
After reading this, the reader will be able to/believe/decide ______ because ______.
Reject promises that are only awareness goals such as "understand X" unless paired with a concrete change in judgment, behavior, or implementation.
Useful promise types:
- Teach a repeatable technique
- Reframe a common misconception
- Prove a capability with evidence
- Compare tradeoffs so the reader can decide
- Show how to solve a painful implementation problem
- Explain why a recent change matters now
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.
- 11d ago First seen · 180 lines · 91 tokens per session scan A 5d9e408fc02d
blog-scope-refiner is a skill published in the GitHub repository prrao87/agent-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 91 tokens to every session and 1,398 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-31.
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…