Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sun2443/designer-skillsnpx agentmods add skills/sun2443/designer-skills/competitive-briefWrote 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/sun2443/designer-skills/competitive-brief)<a href="https://agentmods.dev/skills/sun2443/designer-skills/competitive-brief"><img src="https://agentmods.dev/badge/skills/sun2443/designer-skills/competitive-brief/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/sun2443/designer-skills/competitive-brief"><img src="https://agentmods.dev/badge/skills/sun2443/designer-skills/competitive-brief.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.00055 | $0.02832 |
| Opus 5.5 | $0.00022 | $0.01133 |
| Sonnet 5.5 | $0.00011 | $0.00566 |
| Haiku 4.5 | $0.00006 | $0.00283 |
Grade A, and why
competitive-brief 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 13d 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.
This is a copy
100% identical to competitive-brief — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 332 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitive Brief
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Research competitors and generate a structured competitive analysis comparing positioning, messaging, content strategy, and market presence.
Trigger
User runs /competitive-brief or asks for a competitive analysis, competitor research, or market comparison.
Inputs
Gather the following from the user:
-
Competitor name(s) — one or more competitors to analyze (required)
-
Your company/product context (optional but recommended):
- What you sell and to whom
- Your positioning or value proposition
- Key differentiators you want to highlight
-
Focus areas (optional — if not specified, cover all):
- Messaging and positioning
- Product and feature comparison
- Content and thought leadership strategy
- Recent announcements and news
- Pricing and packaging (if publicly available)
- Market presence and audience
Research Process
For each competitor, research using web search:
- Company website — homepage messaging, product pages, about page, pricing page
- Recent news — press releases, funding announcements, product launches, partnerships (last 6 months)
- Content strategy — blog topics, resource types, social media presence, webinars, podcasts
- Review sites and comparisons — third-party comparisons, analyst mentions, customer review themes
- Job postings — hiring signals that indicate strategic direction (optional)
Research Sources
Gather intelligence from these categories of sources:
Primary Sources (Direct from Competitor)
- Website: homepage, product pages, pricing, about page, careers
- Blog and resource center: content themes, publishing frequency, depth
- Social media profiles: messaging, engagement, content strategy
- Product demos and free trials: UX, features, onboarding experience
- Webinars and events: topics, speakers, audience engagement
- Press releases and newsroom: announcements, partnerships, milestones
- Job postings: hiring signals that reveal strategic priorities (e.g., hiring for a new product line or market)
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.
- 13d ago First seen · 332 lines · 55 tokens per session scan A c1e5442facbc
competitive-brief is a skill published in the GitHub repository sun2443/designer-skills (0 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 55 tokens to every session and 2,832 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to competitive-brief, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…