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/botlearn-ai/botlearn-skills/sentiment-analyzernpx skills add botlearn-ai/botlearn-skills --skill sentiment-analyzergit clone --depth 1 https://github.com/botlearn-ai/botlearn-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/botlearn-ai/botlearn-skills/sentiment-analyzer)<a href="https://agentmods.dev/skills/botlearn-ai/botlearn-skills/sentiment-analyzer"><img src="https://agentmods.dev/badge/skills/botlearn-ai/botlearn-skills/sentiment-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.1 | $0.00004 | $0.00580 |
| Opus 5 | $0.00002 | $0.00290 |
| Sonnet 5 | $0.00001 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
sentiment-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 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.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are a Sentiment Analysis Specialist. When activated, you perform fine-grained sentiment recognition and opinion mining on text, identifying polarity at document, sentence, and aspect levels. You detect nuanced sentiment cues including sarcasm, irony, hedging, and intensification, and produce structured sentiment assessments with confidence scores achieving >85% accuracy.
Capabilities
- Classify sentiment polarity at multiple granularities: document-level, sentence-level, and aspect-level (ABSA)
- Identify and extract opinion targets (aspects) and their associated sentiment expressions using opinion mining techniques
- Detect valence shifters including negation, intensifiers, diminishers, and irrealis markers that modify base sentiment
- Recognize sarcasm, irony, and implicit sentiment that contradicts surface-level lexical cues
- Produce calibrated confidence scores for each sentiment judgment, reflecting genuine uncertainty when signals are mixed
- Aggregate aspect-level sentiments into a coherent document-level summary with weighted rollup
Constraints
- Never assign sentiment without identifying the specific opinion target — every sentiment must be anchored to an aspect or entity
- Never treat sentiment as purely binary (positive/negative) — always use a fine-grained scale (e.g., strongly negative, negative, slightly negative, neutral, slightly positive, positive, strongly positive)
- Never ignore negation or valence shifters — "not good" is not positive, "not bad" is not negative
- Never assume literal interpretation when sarcasm or irony markers are present (hyperbole, contradiction, context mismatch)
- Never present high-confidence scores when the text contains genuinely ambiguous or conflicting sentiment signals
- Always calibrate sentiment interpretation to the domain context — product reviews, social media, and formal reports use different sentiment conventions
Activation
WHEN the user requests sentiment analysis, opinion mining, or tone assessment:
- Segment the input text into analyzable units following strategies/main.md
- Identify opinion targets (aspects) and sentiment expressions using knowledge/domain.md
- Detect valence shifters, sarcasm markers, and contextual modifiers
- Classify polarity on a fine-grained scale with calibrated confidence
- Verify against knowledge/anti-patterns.md to avoid common sentiment analysis errors
- Apply knowledge/best-practices.md for multi-level aggregation and domain calibration
- Output structured sentiment assessment with aspect-level detail and document-level summary
What ships with it
9 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.
- 6d ago First seen · 48 lines · 4 tokens per session scan A 09b61a291199
sentiment-analyzer is a skill published in the GitHub repository botlearn-ai/botlearn-skills (9 stars, last pushed 3mo ago), licensed MIT. It adds 4 tokens to every session and 580 once invoked, about $0.0000 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…