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/fisker086/aiops/redis_toolnpx skills add fisker086/AIOps --skill redis_toolgit clone --depth 1 https://github.com/fisker086/AIOpsWrote 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/fisker086/aiops/redis_tool)<a href="https://agentmods.dev/skills/fisker086/aiops/redis_tool"><img src="https://agentmods.dev/badge/skills/fisker086/aiops/redis_tool.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.00508 |
| Opus 5 | $0.00000 | $0.00254 |
| Sonnet 5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
redis-tool 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.
What it actually says
Redis Tool Skill
Provides comprehensive Redis operations for cache and data management:
- String: get, set, del, keys, exists, type, ttl, expire, incr, decr
- Hash: hget, hset, hdel, hgetall
- List: lpush, rpush, lrange
- Set: sadd, smembers
- ZSet: zadd, zrange
- Info: info, dbsize, ping
Use builtin_redis_tool tool with fields:
operation: Operation name (get, set, del, keys, exists, type, ttl, expire, incr, decr, hash_get, hash_set, hash_del, hash_getall, list_push, list_range, set_add, set_members, zset_add, zset_range, info, dbsize, ping)addr: Redis address (default: localhost:6379)password: (optional) Redis passworddb: (optional) Database number (default: 0)key: Key for string/hash/list/set/zset operationsvalue: Value to setfield: Field for hash operationsttl: TTL in seconds for set/expirepattern: Pattern for keys operation (default: *)score: Score for zset operationsmember: Member for set/zset operationsdirection: List push direction: left/right (default: left)start: Start index for list_range/zset_rangeend: End index for list_range/zset_rangewith_scores: Include scores in zset_range (true/1 or false)section: Info section (e.g., memory, clients)
Example:
operation: get
key: "mykey"
addr: "localhost:6379"
On the AgentSphere desktop app, builtin_redis_tool runs locally via Tauri (run_client_redis_tool); connection parameters stay on the device unless execution is overridden to server in skill settings.
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 · 43 lines · 0 tokens per session scan A 8655bed0fb38
redis-tool is a skill published in the GitHub repository fisker086/AIOps (22 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 508 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 skills, from other repositories
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
moderator-page-migration
Port a moderator page from the main Next.js app (src/pages/moderator/) into apps/moderator. Use when asked to migrate, move or cut over a /moderator/ page to the spoke, or to port its tRPC procedures and Prisma services to SvelteKit loads/actions and Kysely.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…
sql-translate
Translate SQL queries between database dialects (Snowflake, BigQuery, PostgreSQL, MySQL, etc.).