Borrowing it
Nothing to install: this file belongs to prashishh/seo-geo-report-engine. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/prashishh/seo-geo-report-engine/main/.agents/skills/positioning-messaging/SKILL.mdgit clone --depth 1 https://github.com/prashishh/seo-geo-report-engineWrote 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/prashishh/seo-geo-report-engine/positioning-messaging)<a href="https://agentmods.dev/skills/prashishh/seo-geo-report-engine/positioning-messaging"><img src="https://agentmods.dev/badge/skills/prashishh/seo-geo-report-engine/positioning-messaging/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/prashishh/seo-geo-report-engine/positioning-messaging"><img src="https://agentmods.dev/badge/skills/prashishh/seo-geo-report-engine/positioning-messaging.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.00166 | $0.01584 |
| Opus 5 | $0.00083 | $0.00792 |
| Sonnet 5 | $0.00033 | $0.00317 |
| Haiku 4.5 | $0.00017 | $0.00158 |
Grade A, and why
positioning-messaging 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 10d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
positioning-messaging
Owns the GTM/positioning/messaging layer that sits ABOVE SEO — the brand-language spine every
downstream skill currently invents ad hoc. The output is a Positioning & Messaging Pack plus a
canonical messaging: block written back into client.yml. This is qualitative work: no Ahrefs
MCP is required. Competitor language is gathered with WebFetch/WebSearch (and optionally
site-explorer-top-pages to find which competitor pages carry their messaging). Methodology lives in
playbooks/positioning-methodology.md — read it before running. Today is 2026-06-23.
Methodology (PERCEIVE → ANALYZE → VALIDATE → ACT)
PERCEIVE — intake. Resolve the project (./bin/mkt config show --project <client>); read
client.yml for industry, icp, competitors, and the positioning seed. Read any
research/*.md voice-of-customer (reviews, interviews, support tickets, sales-call notes) — VOC is
the evidence base; positioning asserted without it is a guess. For each competitor, WebFetch the
homepage (and its product/pricing page) to capture their headline, category claim, and proof. If you
need to find a competitor's strongest messaging page, site-explorer-top-pages surfaces their
highest-traffic pages (doc the tool first). Note the date of every capture — competitor copy drifts.
ANALYZE — build the architecture. Work the frameworks in order:
- Competitive alternative & category (Dunford). What does the prospect do today if we don't exist (status quo, spreadsheet, rival)? Fill Dunford's 5 components — competitive alternatives, unique attributes, the value those attributes enable, the customers who care most, the market category that frames it — then write Moore's positioning statement: For [target] who [need], [product] is a [category] that [benefit], unlike [alternative], because [proof].
- Messaging House. Roof = one-line value prop. Three pillars = the differentiators (each a benefit, not a feature). Foundation = proof per pillar (metric, customer, mechanism). Map pillars to VPC pain-relievers/gain-creators and the SB7 SB7 arc (customer-as-hero, brand-as-guide).
- Copy primitives — 3 variants each: one-liner (SB7: problem → solution → result), tagline (≤5 words), elevator pitch (≤60 words, Raskin "change is coming" stakes framing optional), hero headline. Variants must differ in angle, not wording.
- Say this / not that table: on-brand term, the off-brand term it replaces, and why (commodity language, competitor-owned, or off-positioning).
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.
- 10d ago First seen · 101 lines · 166 tokens per session scan A 3c58374ca582
positioning-messaging is a skill published in the GitHub repository prashishh/seo-geo-report-engine (5 stars, last pushed 2mo ago), licensed MIT. It adds 166 tokens to every session and 1,584 once invoked, about $0.0008 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
content-amplifier
Use when the user asks to "amplify influencer content with paid media", "set up whitelisting or Spark Ads", "decide which posts to boost", "repurpose influencer content", "turn one video into multiple ads", or "build a UGC asset library"; produces (paid mode) a content-selection scorecard, a paid amplification…
campaign-planner
Use when the user asks to "plan an influencer campaign", "build a campaign blueprint", "track or close a creator campaign", or "record a late campaign correction"; produces the plan and, when requested, a non-canonical evidence tracker with scoped identity, publication, reconciliation, close, and reopen receipts. Not…
cold-outbound-sequencer
Use when the user asks to "build a B2B cold-outbound sequence", "design reply-triage branching", "plan a domain warmup / sending throttle", or "make my outbound CAN-SPAM / opt-in compliant"; produces a multi-step outbound sequence with reply-triage branches (positive / objection / referral / not-now / opt-out), a…
inbox-placement-monitor
Use when the user asks to "track where my emails are actually landing after I send", "read my seed-list inbox vs spam vs promotions results", "trend my Gmail Postmaster / Microsoft SNDS reputation", or "did placement drop after my last send"; produces a per-provider inbox/spam/promotions placement read, a domain/IP…
subject-line-lab
Use when the user asks to "generate subject line variants", "pre-score my subject lines", or "will this subject get truncated / trigger spam filters"; produces a labeled subject + preheader variant set and a per-variant heuristic pre-score card — spam-trigger flags, length/truncation across desktop + mobile…
email-sequence-designer
Use when the user asks to "design a welcome flow", "set up an abandoned-cart sequence", "build a light re-engagement branch inside a lifecycle flow", or "plan a cold-outbound sequence"; produces general lifecycle automation flows (welcome, cart, browse-abandon, post-purchase, in-flow re-engagement, B2B cold outbound)…