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 boshi-xixixi/TraeSkill --skill gtm-positioning-strategygit clone --depth 1 https://github.com/boshi-xixixi/TraeSkillWrote 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/boshi-xixixi/traeskill/gtm-positioning-strategy)<a href="https://agentmods.dev/skills/boshi-xixixi/traeskill/gtm-positioning-strategy"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/gtm-positioning-strategy/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/boshi-xixixi/traeskill/gtm-positioning-strategy"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/gtm-positioning-strategy.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.00057 | $0.03150 |
| Opus 5 | $0.00028 | $0.01575 |
| Sonnet 5 | $0.00011 | $0.00630 |
| Haiku 4.5 | $0.00006 | $0.00315 |
Grade A, and why
gtm-positioning-strategy 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- positioning-strategy — 97% identical, 5 lines differ
How it starts
The opening of the file, as written. The whole thing — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Positioning Strategy
Find and own a defensible market position. Turn generic messaging into clear differentiation — or at least test whether your differentiation actually resonates before committing to it.
When to Use
Triggers:
- "Our messaging sounds exactly like competitors"
- "Brand awareness is strong but conversion is weak"
- "Sales team can't explain why we're different"
- "Buyers see us as interchangeable"
- "Should we reposition before we rebrand?"
- "How do we test positioning claims?"
Context:
- Competitive markets with similar offerings
- Messaging that isn't converting
- New product launches
- Repositioning existing products
- Sales team reports buyer confusion
Core Frameworks
1. One Word Can Change Everything (The "Autonomous" Problem)
The Pattern:
Early enterprise conversations for an autonomous AI product. Positioned as "autonomous AI agent."
Developers: "Cool, but scary." Managers: "Will this replace our team?" Deal progression: Slow. Lots of "we'll think about it."
The Change:
One word: "autonomous" → "AI teammate"
Same product. Same capabilities. Different framing.
Result:
Developers: "This helps me." Managers: "This makes my team more productive." Deal progression: Measurably faster.
Why This Matters:
Positioning isn't what you do. It's what you don't say.
We could've said "replaces developers" (technically true for some tasks). Would've killed every enterprise deal.
The Framework: Word Choice Shapes Buyer Psychology
Words that scare enterprises:
- Autonomous (implies: no control, replacing humans)
- Replaces (threatens: job security)
- Fully automated (removes: human judgment)
- AI-first (means: unclear, buzzword)
Words that convert:
- Teammate (implies: collaboration, helping)
- Augments (helps: makes humans better)
- You stay in control (reassures: human oversight)
- Handles repetitive work (specific: saves time)
How to Test Word Choice:
Don't guess. Test.
Test 1: Outbound Email A/B
- Send 100 prospects Version A ("autonomous agent")
- Send 100 prospects Version B ("AI teammate")
- Measure: Reply rate, meeting booked rate
- Signal strength: High (real buyer intent)
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.
- 6d ago First seen · 439 lines · 57 tokens per session scan A 332c1426936c
gtm-positioning-strategy is a skill published in the GitHub repository boshi-xixixi/TraeSkill (262 stars, last pushed 4mo ago), licensed MIT. It adds 57 tokens to every session and 3,150 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-09-03.
Other skills, from other repositories
<skill-name>
A template for defining a coding-agent skill, including its title, trigger situations, overview, workflow, common mistakes, and optional references.
spec-writing
A method for writing a software specification: a document that records decisions, reasons, boundaries, and ways to judge whether implementation succeeded. It first checks whether important unknowns require user clarification or technical research.
onboarding-unknown-codebase
A method for quickly understanding an unfamiliar codebase, meaning a software project whose structure and behavior you do not yet know. It builds a project map by examining overview files, directories, and one main execution path.
commit-message
A guide for writing clear, traceable Git commit messages using the Conventional Commits format, which labels changes such as features, bug fixes, documentation, and refactoring.
clarifying-questions
Guidance for clarifying vague or assumption-heavy requests before making changes.
debugging
A systematic method for finding the underlying cause of a software bug by observing the failure, forming a hypothesis, and testing it.