Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add octavehq/lfgtm/plugin install octaveWrote 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/octavehq/lfgtm/positioning)<a href="https://agentmods.dev/skills/octavehq/lfgtm/positioning"><img src="https://agentmods.dev/badge/skills/octavehq/lfgtm/positioning/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/octavehq/lfgtm/positioning"><img src="https://agentmods.dev/badge/skills/octavehq/lfgtm/positioning.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.00116 | $0.06264 |
| Opus 5 | $0.00058 | $0.03132 |
| Sonnet 5 | $0.00023 | $0.01253 |
| Haiku 4.5 | $0.00012 | $0.00626 |
Grade A, and why
positioning 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 9d 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 — 575 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/octave:positioning - Positioning & Messaging System
Generate positioning systems and messaging frameworks — from a complete 8-section visual HTML positioning document to standalone text-based messaging artifacts like frameworks, matrices, elevator pitches, positioning statements, narrative arcs, and value prop hierarchies. Everything is pulled from your Octave library and grounded in real conversation evidence.
Key differentiators:
- vs
/octave:deck-- deck is a presentation for an audience; positioning is a reference document - vs
/octave:research-- research is account-specific; positioning is about YOUR product/company
Modes
The skill has two categories of output: the full positioning system (visual HTML) and standalone messaging artifacts (text-based).
POSITIONING SYSTEM (HTML output)
/octave:positioning # Full 8-section positioning system (default)
/octave:positioning full # Same as above
/octave:positioning system # Same as above
/octave:positioning message-framework # Section 1: Message Framework pyramid
/octave:positioning anchors # Section 2: Positioning Anchors
/octave:positioning strategy # Section 3: Positioning Strategy table
/octave:positioning personas # Section 4: Persona-Based Messaging
/octave:positioning awareness # Section 5: Value Prop by Awareness Stage
/octave:positioning use-cases # Section 6: Use Case Messaging Canvas
/octave:positioning lifecycle # Section 7: Use Case Lifecycle
/octave:positioning homepage # Section 8: Homepage Messaging
MESSAGING ARTIFACTS (text output)
/octave:positioning framework # Messaging framework: pillars, proof points, key messages by audience
/octave:positioning matrix # Persona x use case messaging matrix
/octave:positioning elevator-pitch # Elevator pitches (15s/30s/60s/2min)
/octave:positioning narrative # Company/product narrative arc
/octave:positioning value-props # Value proposition hierarchy
/octave:positioning statement # Positioning statement with variations
What ships with it
9 files 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.
- references/elevator-pitches.md 1.1 KB
- references/html-scaffold.md 11 KB
- references/messaging-framework.md 2.6 KB
- references/messaging-matrix.md 2.1 KB
- references/narrative-arc.md 1.3 KB
- references/positioning-statement.md 919 B
- references/section-layouts.md 12 KB
- references/section-templates.md 39 KB
- references/value-prop-hierarchy.md 1.4 KB
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.
- 9d ago First seen · 575 lines · 116 tokens per session scan A 70b479bdd30e
positioning is a skill published in the GitHub repository octavehq/lfgtm (11 stars, last pushed 19d ago), licensed MIT. It adds 116 tokens to every session and 6,264 once invoked, about $0.0006 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…
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…