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/legendtkl/agentic-skill-router/skill-032npx skills add legendtkl/agentic-skill-router --skill skill-032git clone --depth 1 https://github.com/legendtkl/agentic-skill-routerWrote 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/legendtkl/agentic-skill-router/skill-032)<a href="https://agentmods.dev/skills/legendtkl/agentic-skill-router/skill-032"><img src="https://agentmods.dev/badge/skills/legendtkl/agentic-skill-router/skill-032.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.00023 | $0.00543 |
| Opus 5 | $0.00012 | $0.00271 |
| Sonnet 5 | $0.00005 | $0.00109 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
skill-032 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 5d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Text Sentiment Analysis
Analyze customer reviews and extract sentiment scores to understand customer opinions and trends over time.
Problem
Given a dataset of customer reviews, the goal is to evaluate the sentiment (positive, negative, neutral) expressed in each review. This provides valuable insights into customer satisfaction and product performance.
Methodology
- Text Preprocessing: Clean and prepare the text data by removing stop words, punctuation, and applying lemmatization.
- Sentiment Scoring: Use pre-trained sentiment analysis models or libraries to score the sentiment of each review.
- Aggregation: Summarize sentiment scores by product category to identify trends and areas for improvement.
Output
A DataFrame with added columns:
review: Original customer reviewsentiment_score: Float sentiment score (e.g., from -1 to 1)sentiment_label: Categorical sentiment label (positive, negative, neutral)
Installation
pip install pandas numpy nltk transformers
python -c "import nltk; nltk.download('stopwords')"
3-Step Pipeline
Step 1: Load and Preprocess Reviews (step1_load_and_preprocess.py)
- Input: CSV file of customer reviews with a
reviewcolumn. - Process: Normalize text, tokenize words, remove stop words, and lemmatize.
- Output: Cleaned DataFrame with
reviewcolumn ready for analysis.
Step 2: Analyze Sentiment (step2_sentiment_analysis.py)
- Input: Cleaned DataFrame from Step 1.
- Process: Apply sentiment analysis model to generate scores and labels for each review.
- Output: DataFrame with added
sentiment_scoreandsentiment_labelcolumns.
Step 3: Summarize Results (step3_aggregate_results.py)
- Input: DataFrame from Step 2.
- Process: Group by product category and compute average sentiment scores.
- Output: Summary DataFrame of average sentiment scores by category.
# Example of sentiment analysis using Hugging Face Transformers
from transformers import pipeline
# Load sentiment analysis pipeline
sentiment_pipeline = pipeline('sentiment-analysis')
# Example review
review = "This product is amazing!"
result = sentiment_pipeline(review)
print(result)
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.
- 5d ago First seen · 64 lines · 23 tokens per session scan A a866b38c232e
skill-032 is a skill published in the GitHub repository legendtkl/agentic-skill-router (5 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 543 once invoked, about $0.0001 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…
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…