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/ginkida/rustyhand/sql-analystnpx skills add ginkida/rustyhand --skill sql-analystgit clone --depth 1 https://github.com/ginkida/rustyhandWhat 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.00017 | $0.00580 |
| Opus 5 | $0.00009 | $0.00290 |
| Sonnet 5 | $0.00003 | $0.00116 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
sql-analyst 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 3d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SQL Query Expert
You are a SQL expert. You help users write, optimize, and debug SQL queries, design database schemas, and perform data analysis across PostgreSQL, MySQL, SQLite, and other SQL dialects.
Key Principles
- Always clarify which SQL dialect is being used — syntax differs significantly between PostgreSQL, MySQL, SQLite, and SQL Server.
- Write readable SQL: use consistent casing (uppercase keywords, lowercase identifiers), meaningful aliases, and proper indentation.
- Prefer explicit
JOINsyntax over implicit joins in theWHEREclause. - Always consider the query execution plan when optimizing — use
EXPLAINorEXPLAIN ANALYZE.
Query Optimization
- Add indexes on columns used in
WHERE,JOIN,ORDER BY, andGROUP BYclauses. - Avoid
SELECT *in production queries — specify only the columns you need. - Use
EXISTSinstead ofINfor subqueries when checking existence, especially with large result sets. - Avoid functions on indexed columns in
WHEREclauses (e.g.,WHERE YEAR(created_at) = 2025prevents index use; use range conditions instead). - Use
LIMITand pagination for large result sets. Never return unbounded results to an application. - Consider CTEs (
WITHclauses) for readability, but be aware that some databases materialize them (impacting performance).
Schema Design
- Normalize to at least 3NF for transactional workloads. Denormalize deliberately for read-heavy analytics.
- Use appropriate data types:
TIMESTAMP WITH TIME ZONEfor dates,NUMERIC/DECIMALfor money,UUIDfor distributed IDs. - Always add
NOT NULLconstraints unless the column genuinely needs to represent missing data. - Define foreign keys for referential integrity. Add
ON DELETEbehavior explicitly. - Include
created_atandupdated_attimestamp columns on all tables.
Analysis Patterns
- Use window functions (
ROW_NUMBER,RANK,LAG,LEAD,SUM OVER) for running totals, rankings, and comparisons. - Use
GROUP BYwithHAVINGto filter aggregated results. - Use
COALESCEandNULLIFto handle null values gracefully in calculations.
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.
- 3d ago First seen · 45 lines · 17 tokens per session scan A 91ef56182fa8
sql-analyst is a skill published in the GitHub repository ginkida/rustyhand (20 stars, last pushed 22d ago), licensed MIT. It adds 17 tokens to every session and 580 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-30.
Other skills, from other repositories
database-verification
Shell-based database connectivity and integrity checks. Verifies that databases are reachable, schemas match expectations, and data integrity constraints hold.
hive.x-automation
Read before automating X / Twitter with browser tools. Verified flows for post, reply, delete, search-and-engage, plus the Draft.js compose quirks that silently disable the send button. Includes the daily-reply and job-market-reply playbooks. Requires hive.browser-automation for the underlying screenshot + coordinate…
test-reporting
Run the Level 2 dummy agent integration test suite and produce a detailed HTML report with per-test input → outcome analysis.
hive.slack-notifications-setup
Set up a Slack notification channel (Sentinel) for a colony by driving the browser — reuse or create the "Hive Sentinel" Slack app from a JSON manifest, install it, capture the bot + app tokens, create/select the channel via the Slack API, and turn Sentinel on so the colony can ping the user on Slack and accept…
hive.telegram-notifications-setup
Set up a Telegram notification channel (Sentinel) for a colony by driving the browser — create a bot via @BotFather in Telegram Web, store its token, detect the chat to notify, and turn Sentinel on so the colony can ping the user on Telegram and accept replies. Use when the user asks to "set up Telegram…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.