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 agentmods add skills/jayrha/agentskills/swot-analyzernpx skills add JayRHa/AgentSkills --skill swot-analyzergit clone --depth 1 https://github.com/JayRHa/AgentSkillsWrote 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/jayrha/agentskills/swot-analyzer)<a href="https://agentmods.dev/skills/jayrha/agentskills/swot-analyzer"><img src="https://agentmods.dev/badge/skills/jayrha/agentskills/swot-analyzer.svg" alt="Measured on agentmods" 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 | $0.00121 | $0.01678 |
| Opus 5 | $0.00060 | $0.00839 |
| Sonnet 5 | $0.00024 | $0.00336 |
| Haiku 4.5 | $0.00012 | $0.00168 |
Grade A, and why
swot-analyzer 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 yesterday.
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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SWOT Analyzer
Overview
This skill builds a high-quality SWOT analysis and — critically — does not stop at four lists. It drives the analysis through to decisions and actions using the TOWS matrix (pairing internal factors with external factors to generate strategies).
Keywords: SWOT, TOWS, strengths, weaknesses, opportunities, threats, strategic planning, competitive analysis, situation analysis, go/no-go, market entry, business strategy.
Use this skill whenever the user wants to evaluate a situation, position, or decision and translate that evaluation into a plan.
Core principle: Strengths and Weaknesses are INTERNAL and present-tense (under the subject's control: people, capabilities, IP, costs, brand). Opportunities and Threats are EXTERNAL and future-leaning (outside control: market, competitors, regulation, technology, economy). Mixing these up is the single most common SWOT failure.
Workflow
Follow these steps in order. Do not skip the scoping or the TOWS step.
-
Scope the subject. Confirm WHO/WHAT is being analyzed (company, product, team, initiative, person) and the DECISION or GOAL it serves (e.g., "decide whether to enter the EU market"). A SWOT with no decision attached is just a list. If the user did not state a goal, ask one short clarifying question or state an assumed goal explicitly.
-
Gather evidence. Pull facts: financials, market data, customer feedback, competitor moves, internal capabilities. Prefer specific, evidenced claims over vague adjectives. If information is missing, mark it as an assumption.
-
Populate the four quadrants. For each quadrant, generate factors using the prompts in
references/prompts.md. Apply the internal/external and present/future tests. Aim for 4-8 high-signal items per quadrant, not 20 weak ones. -
Make each factor concrete. Quantify where possible ("churn at 7% monthly", not "retention issues"). Attribute strengths/weaknesses to a cause. Tie opportunities/threats to a trend with a rough magnitude and time horizon.
What ships with it
6 files 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.
- yesterday First seen · 96 lines · 121 tokens per session scan A ed79b0361592
swot-analyzer is a skill published in the GitHub repository JayRHa/AgentSkills (4 stars, last pushed 1mo ago), licensed MIT. It adds 121 tokens to every session and 1,678 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-09-03.
Other skills, from other repositories
reverse-engineering-tools
Guide for reverse engineering protected games and anti-cheat components across user mode, kernel mode, and hypervisor-aware environments. Use this skill when analyzing drivers, IOCTL protocols, callback registration, injected-code artifacts, integrity checks, protected binaries, or debugging security-sensitive game…
backend-builder
Используй только внутри активного Codex Project Autopilot-проекта по утверждённому плану; не включай для обычных backend-задач вне автопилота.
project-plan
Turn a product goal or feature request into a clear Agiflow project plan with small, testable tasks in Planning status. Use when starting a project, decomposing a feature, clarifying requirements, or converting an idea into an actionable backlog.
getting-started
Assess an authenticated Agiflow workspace and recommend the right next project-management workflow. Use when a user is new to Agiflow, asks what to do next, needs orientation, or is unsure whether to plan, refine, groom, triage, or review daily status.
openclaw-debugger
Trigger when an OpenClaw agent is broken, silent, crashing, stuck, not responding, returning empty output, or the user says "my agent is down", "agent not working", "/openclaw-debugger". Walks through the standard OpenClaw 2026.4 diagnosis checklist and prints a report.
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.