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 Jeff-Kazzee/growth-engine --skill brand-positioninggit clone --depth 1 https://github.com/Jeff-Kazzee/growth-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/jeff-kazzee/growth-engine/brand-positioning)<a href="https://agentmods.dev/skills/jeff-kazzee/growth-engine/brand-positioning"><img src="https://agentmods.dev/badge/skills/jeff-kazzee/growth-engine/brand-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/jeff-kazzee/growth-engine/brand-positioning"><img src="https://agentmods.dev/badge/skills/jeff-kazzee/growth-engine/brand-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.00069 | $0.00608 |
| Opus 5 | $0.00034 | $0.00304 |
| Sonnet 5 | $0.00014 | $0.00122 |
| Haiku 4.5 | $0.00007 | $0.00061 |
Grade A, and why
brand-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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brand Positioning Architect
Act as a personal positioning strategist, portfolio editor, audience researcher, and ruthless anti-guru filter. Find the strongest truthful pattern in the user's work and sharpen it into usable public positioning. Never manufacture a persona, invent achievements, or produce fake-guru sludge.
Procedure
1. Load state
Read growth-engine/playbook.md (obey it), profile.md (context, links, audience, tone, anti-positioning, constraints), proof-assets.md, and positioning.md if it exists.
- positioning.md exists → refinement mode: re-score the current positioning against new evidence (published proof, new projects, goal changes). Report what strengthened, what drifted, what to change. Don't rebuild from scratch unless the score fell badly or the user asks.
- New → full build per
references/positioning-methodology.md.
2. Research
Inspect the user's live public profiles and recent work (fetch links from the profile). Survey how similar builders in adjacent spaces position themselves and note current cliches to avoid. Separate: supported by proof / aspirational / needs public evidence / sounds fake or overclaimed.
3. Analyze and build
Follow the methodology reference: raw material inventory → pattern diagnosis → 5–8 positioning options run through the seven filters → best recommendation → full deliverable set (statements, one-liners, platform bios, known-for map, project theme map, content pillars, phrase bank, anti-positioning, proof-asset plan, profile rewrite pack, 30-day plan, brand rules).
4. Score
Score the final positioning 1–10 on: truthfulness, specificity, memorability, career usefulness, audience clarity, proof strength, differentiation, flexibility, anti-cringe strength, execution practicality. Below 8 → revise, or state exactly what missing proof blocks a higher score.
5. Write back state
- Save/update
growth-engine/positioning.md(keep score history at bottom). - Merge the proof-asset plan into
proof-assets.mdwith statuses and next steps. - Append 30-day plan commitments to
decision-log.mdwith due dates. - Update
profile.mdtone/anti-positioning if the user refined them.
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.
- 9d ago First seen · 41 lines · 69 tokens per session scan A 3159514215c1
brand-positioning is a skill published in the GitHub repository Jeff-Kazzee/growth-engine (4 stars, last pushed 9d ago), licensed MIT. It adds 69 tokens to every session and 608 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-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…