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 ur-grue/autopunk-media-skills --skill niche-positioning-briefgit clone --depth 1 https://github.com/ur-grue/autopunk-media-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/ur-grue/autopunk-media-skills/niche-positioning-brief)<a href="https://agentmods.dev/skills/ur-grue/autopunk-media-skills/niche-positioning-brief"><img src="https://agentmods.dev/badge/skills/ur-grue/autopunk-media-skills/niche-positioning-brief/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/ur-grue/autopunk-media-skills/niche-positioning-brief"><img src="https://agentmods.dev/badge/skills/ur-grue/autopunk-media-skills/niche-positioning-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00062 | $0.01885 |
| Opus 5 | $0.00031 | $0.00942 |
| Sonnet 5 | $0.00012 | $0.00377 |
| Haiku 4.5 | $0.00006 | $0.00188 |
Grade A, and why
niche-positioning-brief 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Niche Positioning Brief
What This Skill Does
Writes a concise positioning brief that defines a newsletter's niche, primary differentiator, target reader, editorial promise, and what the publication refuses to do — giving the editor a clear decision-making framework and a document that can anchor copy across subscribe pages, pitches, and About pages.
When To Use This Skill
- You are launching a new newsletter and want to establish positioning before writing any copy or content
- Your newsletter has been running for a while but has drifted or blurred — you are no longer sure what it stands for or who exactly it is for
- You are rebranding or repositioning after a significant change in direction
- You are bringing in a co-writer or editor and need a shared positioning document to align on before they start writing
- You want a document to guide difficult editorial decisions: "should I cover X?" — a positioning brief answers that question without requiring a judgment call every time
What You Need To Provide
Required: What the newsletter covers (broad subject area); who you are writing for (even a rough description of the reader you have in mind); why you are starting or running this newsletter (the genuine motivation, not the marketing version); what existing newsletters cover the same ground (at least one — if you cannot name a competitor, the niche may be undefined) Optional: What you refuse to cover or how you refuse to cover it; any reader feedback you have received about what they value most; your own background or expertise and why it qualifies you for this subject; what you want the newsletter to be known for in three years
How the Assistant Approaches This
- Identifies the positioning territory: given the subject area and the competitor landscape, where is the gap? Not every newsletter needs an entirely unclaimed space — positioning can be about how you approach a subject, not just what you cover
- Defines the target reader with specificity — not a demographic ("35–50, college educated") but a psychographic and situational description: what does this reader already know, what are they frustrated by, what would make them forward this to a colleague?
- Articulates the editorial promise in one sentence: the thing the newsletter commits to delivering in every edition. This sentence should be testable against any piece of content — you should be able to ask "does this edition fulfil the promise?" and get a clear yes or no
- Defines the negative space: what the newsletter will not do. The exclusions are as important as the inclusions — they protect the positioning from scope creep and give the editor a clear mandate to decline off-topic work
- Synthesises the above into a positioning brief with an internal use version (the decision-making document) and a short external version (usable in an About page or subscribe page description)
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 · 115 lines · 62 tokens per session scan A 20e1ed4251f4
niche-positioning-brief is a skill published in the GitHub repository ur-grue/autopunk-media-skills (32 stars, last pushed 12d ago), licensed MIT. It adds 62 tokens to every session and 1,885 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-09-04.
Other skills, from other repositories
competitive-analyzer
Structured competitive teardown for product discovery - surface the 4-6 dimensions buyers actually weigh, score every competitor on each, and identify exploitable gaps. Use when: competitive analysis, competitor teardown, market positioning, where do we win, where do we lose, competitive gap analysis, competitor audit.
purple-cow-audit
Score product remarkability 1-10 to decide if it's worth promoting. Seth Godin's Purple Cow test. Triggers on: "is this product worth promoting", "should I promote", "product audit", "purple cow", "remarkable product", "is it remarkable", "rate this product", "product quality check", "worth my reputation", "product…
Product Launch Press Kit
Generate a product launch press kit from a product brief: a market positioning brief and a launch risk register with mitigations. Use for press kit, launch, positioning, and press release requests.
Market Positioning Analysis
Analyze product market positioning, competitive landscape, and unique value proposition. Use for positioning, market analysis, and differentiation.
show-off
Create polished self-contained HTML showcase pages and section screenshots for demos, launch posts, social media, article illustrations, and visual presentations. Use when the user wants to turn a project, feature, case study, markdown brief, or prompt into a bilingual scrollable showcase with reusable promo images.
Newsletter Summary Writer
Condenses long articles, threads, or documents into concise, engaging newsletter-ready summaries.