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 skills add legendtkl/agentic-skill-router --skill skill-094git 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-094)<a href="https://agentmods.dev/skills/legendtkl/agentic-skill-router/skill-094"><img src="https://agentmods.dev/badge/skills/legendtkl/agentic-skill-router/skill-094/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/legendtkl/agentic-skill-router/skill-094"><img src="https://agentmods.dev/badge/skills/legendtkl/agentic-skill-router/skill-094.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.00032 | $0.01606 |
| Opus 5 | $0.00016 | $0.00803 |
| Sonnet 5 | $0.00006 | $0.00321 |
| Haiku 4.5 | $0.00003 | $0.00161 |
Grade C, and why
skill-094 scanned grade C with 2 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 7d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf /app/current/* Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:3000/health How it starts
The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment Procedures
⚠️ CRITICAL SKILL: This skill handles production deployments. Always follow procedures carefully.
Overview
This skill provides step-by-step procedures for safe production deployments.
Pre-Deployment Checklist
Before ANY deployment, verify:
## Pre-Deployment Checklist
### Code Quality
- [ ] All tests passing (unit, integration, e2e)
- [ ] Code reviewed and approved
- [ ] No linting errors
- [ ] No TypeScript errors
- [ ] No console.log statements
### Build
- [ ] Production build successful
- [ ] Bundle size acceptable
- [ ] No build warnings
### Environment
- [ ] All environment variables configured
- [ ] Secrets up to date
- [ ] Database migrations ready
- [ ] Feature flags set correctly
### Communication
- [ ] Team notified of deployment
- [ ] Stakeholders informed (if major)
- [ ] Support team aware
### Safety
- [ ] Rollback plan documented
- [ ] Database backup completed
- [ ] Current version noted
- [ ] Monitoring dashboard open
Deployment Workflow
Step 1: BACKUP
# Note current version
pm2 list
git log -1 --oneline
# Backup current deployment
cp -r /app/current /backup/app-$(date +%Y%m%d-%H%M%S)
# Database backup (if applicable)
pg_dump -h localhost -U dbuser dbname > backup-$(date +%Y%m%d).sql
Step 2: BUILD
# Pull latest code
git pull origin main
# Install dependencies
npm ci --production
# Build application
npm run build
# Run migrations (if any)
npm run migrate
Step 3: DEPLOY
# Reload with zero-downtime
pm2 reload ecosystem.config.js --update-env
# Or for Docker
docker-compose pull
docker-compose up -d
Step 4: VERIFY
# Check process status
pm2 list
# Check health endpoint
curl -s http://localhost:3000/health
# Check logs for errors
pm2 logs app-name --lines 50
# Verify key endpoints
curl -s http://localhost:3000/api/status
Step 5: CONFIRM OR ROLLBACK
If issues detected → Execute Rollback Procedure
If all good → Confirm deployment complete
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.
- 7d ago First seen · 274 lines · 32 tokens per session scan C 75e957646f24
skill-094 is a skill published in the GitHub repository legendtkl/agentic-skill-router (5 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 1,606 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.