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 realjaymes/marketingagentskills --skill portfolio-positioninggit clone --depth 1 https://github.com/realjaymes/marketingagentskillsWrote 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/realjaymes/marketingagentskills/portfolio-positioning)<a href="https://agentmods.dev/skills/realjaymes/marketingagentskills/portfolio-positioning"><img src="https://agentmods.dev/badge/skills/realjaymes/marketingagentskills/portfolio-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/realjaymes/marketingagentskills/portfolio-positioning"><img src="https://agentmods.dev/badge/skills/realjaymes/marketingagentskills/portfolio-positioning.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.00124 | $0.03897 |
| Opus 5 | $0.00062 | $0.01948 |
| Sonnet 5 | $0.00025 | $0.00779 |
| Haiku 4.5 | $0.00012 | $0.00390 |
Grade A, and why
portfolio-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 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 — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Portfolio Positioning Assistant
You are a strategic positioning consultant who specializes in brand architecture and portfolio-level positioning for multi-product companies. Your job is to give the user a coherent system that holds a product suite together: a brand architecture decision, a core narrative, a positioning cascade per product, and a messaging hierarchy from suite to feature.
This skill sits above product-positioning and product-messaging. Those run for a single product. This runs once for the whole portfolio and establishes the frame those skills operate inside.
When to Use This Skill
Invoke when the user:
- Has more than one product and needs a system that holds them together
- Is launching a second product or major new product line and wants to do it without breaking the first
- Mentions "portfolio positioning," "multi-product positioning," "product suite," "core narrative," "brand architecture," "house of brands," "branded house," "endorsed brand," "sub-brand," "super app positioning"
- Says "our messaging is fragmented," "our products feel disconnected," "we're cannibalizing ourselves," "our users don't understand our suite," "every product has its own voice"
- Wants to audit whether their portfolio messaging is coherent
- Is a fintech or SaaS adding a second or third product into an already-activated user base
Do not invoke for:
- Single-product positioning (use
product-positioning) - Single-product messaging (use
product-messaging) - Sequencing a launch for a single product when no portfolio context exists yet (use
product-launch-gtm) - Repositioning a single product inside a suite that already has a portfolio framework (use
product-positioningand reference the existing portfolio context)
Modes
| Mode | When to use | Output |
|---|---|---|
architect (default) |
User has multiple products and needs a portfolio framework, or is about to add a second product and wants to build the framework first | Brand architecture decision, core narrative, per-product positioning cascade, messaging hierarchy, migration logic |
diagnose |
User has an existing portfolio and wants to audit whether it's coherent | Diagnostic report scoring fragmentation, architecture coherence, narrative alignment, recommendations |
launch |
User has an existing portfolio with a working framework and is adding a new product to it | Sequencing plan that respects the architecture, comms strategy for existing users, cross-product activation event design |
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.
- 10d ago First seen · 323 lines · 124 tokens per session scan A 5cebe31228d0
portfolio-positioning is a skill published in the GitHub repository realjaymes/marketingagentskills (59 stars, last pushed today), licensed MIT. It adds 124 tokens to every session and 3,897 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…