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 commands/neurofoo/agent-skills/swotgit clone --depth 1 https://github.com/neurofoo/agent-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/commands/neurofoo/agent-skills/swot)<a href="https://agentmods.dev/commands/neurofoo/agent-skills/swot"><img src="https://agentmods.dev/badge/commands/neurofoo/agent-skills/swot.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.00000 | $0.00565 |
| Opus 5 | $0.00000 | $0.00282 |
| Sonnet 5 | $0.00000 | $0.00113 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
swot 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 4d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SWOT Analysis
Perform a strategic analysis examining Strengths, Weaknesses, Opportunities, and Threats.
Instructions
First clarify the subject and objective of the analysis. Then systematically examine each quadrant, considering both internal capabilities and external factors.
Output Format
Subject: What are we analyzing? Objective: What are we trying to achieve?
SWOT Matrix
| Helpful | Harmful | |
|---|---|---|
| Internal | STRENGTHS | WEAKNESSES |
| • [strength 1] | • [weakness 1] | |
| • [strength 2] | • [weakness 2] | |
| • [strength 3] | • [weakness 3] | |
| External | OPPORTUNITIES | THREATS |
| • [opportunity 1] | • [threat 1] | |
| • [opportunity 2] | • [threat 2] | |
| • [opportunity 3] | • [threat 3] |
Strengths (Internal, Positive) What advantages do you have? What do you do well? What resources do you have? What do others see as your strengths?
Weaknesses (Internal, Negative) What could you improve? What do you lack? What do others see as weaknesses? Where are you vulnerable?
Opportunities (External, Positive) What trends could you take advantage of? What opportunities are open to you? How can you turn strengths into opportunities?
Threats (External, Negative) What obstacles do you face? What is your competition doing? Are there changing requirements or standards? Could weaknesses threaten your position?
Strategic Combinations
| Combination | Strategy |
|---|---|
| S-O (Strengths → Opportunities) | How to leverage strengths to capture opportunities |
| W-O (Weaknesses ↔ Opportunities) | How opportunities can help overcome weaknesses |
| S-T (Strengths → Threats) | How to use strengths to counter threats |
| W-T (Weaknesses × Threats) | Where you're most vulnerable; what to shore up |
Key Insights Top 3 strategic implications from this analysis.
Recommended Actions Specific next steps based on the SWOT.
Guidelines
- Be honest about weaknesses—this is internal analysis
- Distinguish between current state and potential
- Be specific: "strong brand" is vague; "brand recognized by 80% of target market" is useful
- Consider multiple perspectives when available
- Focus on factors relevant to the objective
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.
- 4d ago First seen · 63 lines · 0 tokens per session scan A 7cc7d71766f4
swot is a command published in the GitHub repository neurofoo/agent-skills (111 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 565 tokens. 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.