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 adam-lagerhausen/b2b-marketing-skills --skill category-point-of-viewgit clone --depth 1 https://github.com/adam-lagerhausen/b2b-marketing-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/adam-lagerhausen/b2b-marketing-skills/category-point-of-view)<a href="https://agentmods.dev/skills/adam-lagerhausen/b2b-marketing-skills/category-point-of-view"><img src="https://agentmods.dev/badge/skills/adam-lagerhausen/b2b-marketing-skills/category-point-of-view/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/adam-lagerhausen/b2b-marketing-skills/category-point-of-view"><img src="https://agentmods.dev/badge/skills/adam-lagerhausen/b2b-marketing-skills/category-point-of-view.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.00046 | $0.03223 |
| Opus 5.5 | $0.00018 | $0.01289 |
| Sonnet 5.5 | $0.00009 | $0.00645 |
| Haiku 4.5 | $0.00005 | $0.00322 |
Grade A, and why
category-point-of-view 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 1mo 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 — 356 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Category Point of View
When to use
Use this skill when you need to build, sharpen, or pressure-test a category point of view for a B2B company, product, campaign, founder narrative, executive content program, or market education motion.
Use it for:
- Defining the problem the company wants to own
- Creating a category narrative before a launch, fundraise, or executive campaign
- Moving beyond a crowded label such as "AI CRM," "AI SDR," "copilot," or "workflow automation"
- Turning product positioning into a broader market belief system
- Building a content strategy that can survive the coming flood of AI-generated slop
- Giving practitioners useful language while giving leaders a reason to care
- Creating a measurement plan for category creation and narrative adoption
Do not use this skill to create a vague brand manifesto, inflated category claim, or thin thought-leadership calendar. A category POV must make a buyer say, "that is exactly the problem we are living with," before it asks them to believe the solution.
Inputs
Ask for or infer as much of the following as possible. If an input is missing, state the assumption and mark confidence as low.
- Company and product name
- Product description and core capabilities
- Existing category or market label
- Target audience: practitioner, buyer, economic buyer, influencer, industry, company size, maturity
- Problem the company wants to own
- Current alternatives, status quo, and competing category labels
- Market shift that makes the problem newly urgent
- Practitioner pains and daily workflows
- Leader-level business consequences
- Differentiated belief, mechanism, data, benchmark, model, community, or proof
- Customer language, stories, objections, and examples
- Existing content, founder opinions, product roadmap, and proof assets
- Distribution channels and founder or executive strengths
- Constraints: claims to avoid, regulated topics, competitive boundaries, launch timing, content capacity
Core principles
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.
- 1mo ago First seen · 356 lines · 46 tokens per session scan A 3a5d25c74d1a
category-point-of-view is a skill published in the GitHub repository adam-lagerhausen/b2b-marketing-skills (6 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 3,223 once invoked, about $0.0002 per session on Opus 5.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
go-to-market-playbook
A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.
skill-catalog
Maintains the central registry of all skills with dependencies, trigger phrases, review gates, and chaining.
gbp-review-strategy
Analyzes review velocity, sentiment distribution, and competitor review patterns, then produces branded response.
design-reviewer
Reviews implemented React/Tailwind/CSS output for design quality across 5 dimensions scored 0-4: anti-patterns.
design-incident-response
Triage decision tree for design incidents flagged by /design-reviewer.
learn
Process raw source material (transcripts, docs, articles, competitor pages, meeting notes) into structured context.