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 Musaraf-M/sentinal --skill sentinal-redisgit clone --depth 1 https://github.com/Musaraf-M/sentinalWrote 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/musaraf-m/sentinal/sentinal-redis)<a href="https://agentmods.dev/skills/musaraf-m/sentinal/sentinal-redis"><img src="https://agentmods.dev/badge/skills/musaraf-m/sentinal/sentinal-redis/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/musaraf-m/sentinal/sentinal-redis"><img src="https://agentmods.dev/badge/skills/musaraf-m/sentinal/sentinal-redis.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.00035 | $0.03018 |
| Opus 5.5 | $0.00014 | $0.01207 |
| Sonnet 5.5 | $0.00007 | $0.00604 |
| Haiku 4.5 | $0.00003 | $0.00302 |
Grade A, and why
sentinal-redis 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 1mo 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 — 332 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sentinal Redis
Monitor Redis server health, BullMQ queues, memory, and performance from any messaging channel. Ask questions in plain English — get actionable diagnostics.
When to Use
✅ USE this skill when:
- User asks about Redis server health, status, or info
- User wants to check memory usage or diagnose OOM issues
- User asks about BullMQ queue depths, failed jobs, or stuck workers
- User wants to inspect slow queries or latency issues
- User asks to diagnose why Redis is slow or unresponsive
- User mentions queue backlog, dead letter queue, or job failures
- User wants a quick health summary of their Redis instance
When NOT to Use
❌ DON'T use this skill when:
- User wants to manage PostgreSQL, MySQL, or other non-Redis databases
- User wants to manage Kafka, RabbitMQ, or SQS queues (not BullMQ)
- User needs help writing application code that uses Redis
- User wants to set up Redis from scratch (use official Redis docs instead)
Safety Rules
⚠️ CRITICAL: This skill is READ-ONLY. No exceptions.
- NEVER run destructive commands (
FLUSHDB,FLUSHALL,DEL,UNLINK,SET,EXPIRE) — even if the user asks. Explain why and suggest they run it manually instead. - NEVER modify Redis configuration (
CONFIG SET) — direct the user to do it themselves. - NEVER print or expose the full
REDIS_URLin output — it may contain passwords. Always mask credentials before displaying. - When in doubt, show the command first and ask for confirmation
Connection
If REDIS_URL is set, use it for all commands:
redis-cli -u "$REDIS_URL" <command>
If REDIS_URL is not set, default to localhost:
redis-cli <command>
For password-protected instances without REDIS_URL:
redis-cli -h <host> -p <port> -a <password> <command>
Always test connectivity first:
redis-cli -u "${REDIS_URL:-redis://localhost:6379}" ping
Server Health
Quick Status
redis-cli -u "${REDIS_URL:-redis://localhost:6379}" ping
What ships with it
2 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.
- 1mo ago First seen · 332 lines · 35 tokens per session scan A 005ed73c14e1
sentinal-redis is a skill published in the GitHub repository Musaraf-M/sentinal (2 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 3,018 once invoked, about $0.0001 per session on Opus 5.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
qdrant-monitoring-debugging
Diagnoses Qdrant production issues using metrics and observability tools. Use when someone reports 'optimizer stuck', 'indexing too slow', 'memory too high', 'OOM crash', 'queries are slow', 'latency spike', or 'search was fast now it's slow'. Also use when performance degrades without obvious config changes.
huawei-cloud-mrs-redis-meta-check
A checker for Redis cluster metadata files named nodes-*.conf. Redis is an in-memory data store, and a cluster uses these files to record nodes, slots, and master-replica relationships.
performance
Use when optimizing application performance — caching strategies, eager loading, query optimization, Redis patterns, or background job design.
troubleshoot-proxysql
Use when diagnosing issues with Proxysql: backend connection starvation, multiplexing collapse, monitor false decisions, query rule cpu overload, or configuration drift. Queries Netdata via MCP for backend server health status, monitor health check results, backend connection pool usage, client connection metrics…
troubleshoot-redis
Use when diagnosing issues with Redis: the fork/cow storm, the event loop wedge, the replication backlog overflow, the memory pressure spiral, or the connection exhaustion cascade. Queries Netdata via MCP for redis reachability, uptime and unexpected restarts, memory usage ratio, memory fragmentation ratio, rejected…
troubleshoot-memcached
Use when diagnosing issues with Memcached: availability, throughput, hit rate & efficiency, or connections degradation. Queries Netdata via MCP for process liveness, unexpected restart (uptime reset), command rates (cmdget, cmdset, cmdtouch), flush all events (cmdflush), cache hit ratio, applies the diagnostic tree…