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 saajunaid/caddis-plugin --skill db-testinggit clone --depth 1 https://github.com/saajunaid/caddis-pluginWrote 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/saajunaid/caddis-plugin/db-testing)<a href="https://agentmods.dev/skills/saajunaid/caddis-plugin/db-testing"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/db-testing/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/saajunaid/caddis-plugin/db-testing"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/db-testing.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.00029 | $0.00632 |
| Opus 5.5 | $0.00012 | $0.00253 |
| Sonnet 5.5 | $0.00006 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
db-testing 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Testing Skill
Specialized skill for testing, debugging, and validating database connectivity and queries.
When to Use
- User reports database connection errors
- Testing a new database configuration
- Validating queries before deployment
- Debugging data retrieval issues
- Verifying authentication configuration
Steps
Step 1: Network Connectivity Check
# Test if server is reachable
ping <DB_HOST>
# Test database port
# SQL Server: 1433, PostgreSQL: 5432, MySQL: 3306
telnet <DB_HOST> <DB_PORT>
Step 2: Connection String Validation
Check environment configuration:
DB_HOST=<server_name>
DB_NAME=<database_name>
DB_USER=<username>
DB_PASSWORD=<password>
DB_DRIVER=<driver_name>
Step 3: Connection Test
# Generic connection test pattern
import os
try:
conn = create_connection(
host=os.getenv("DB_HOST"),
database=os.getenv("DB_NAME"),
user=os.getenv("DB_USER"),
password=os.getenv("DB_PASSWORD"),
)
print("Connection successful!")
cursor = conn.cursor()
cursor.execute("SELECT 1")
print(f"Query test: {cursor.fetchone()}")
conn.close()
except Exception as e:
print(f"Connection failed: {e}")
Step 4: Query Validation
query = "SELECT TOP 5 * FROM <table_name>" # Adjust syntax for your DB
df = pd.read_sql(query, conn)
print(f"Returned {len(df)} rows")
print(df.columns.tolist())
Common Issues & Solutions
| Error | Cause | Solution |
|---|---|---|
| Connection refused | Server unreachable | Check network/VPN, firewall rules |
| Login failed | Auth issue | Verify credentials, check auth mode |
| Invalid connection string | Malformed config | Review driver docs for correct format |
| Certificate error | SSL validation | Configure trust settings for your DB |
| Driver not found | Missing driver | Install appropriate database driver |
Output Format
## Database Connection Test Results
**Server**: `<server>`
**Database**: `<database>`
**Auth Mode**: <auth_type>
| Test | Status | Details |
|------|--------|---------|
| Network ping | Pass/Fail | Response time |
| Port check | Pass/Fail | TCP connection |
| DB connection | Pass/Fail | Driver info |
| Sample query | Pass/Fail | Row count |
**Conclusion**: [Summary]
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 · 118 lines · 29 tokens per session scan A ae3ef78ad602
db-testing is a skill published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed 4d ago), licensed MIT. It adds 29 tokens to every session and 632 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-09-03.
Other skills, from other repositories
goga-prototype-plan-verification
Verification of the assembled architecture plan against the DSL.
goga-change-investigator
Evidence-driven root cause investigation.
goga-change-tracer
Semantic behavior reconstruction via tracing.
rn-debugging
This skill should be used when the user asks to "debug the app", "fix a crash", "diagnose a blank screen", "read error logs", "troubleshoot CDP connection", "check Metro status", "find native crashes", "inspect network failures", "the app crashed", "I see a blank screen", "the screen is white", "something broke", "app…
python-run
Run and debug Python scripts in the project. Use when the user says "run python", "execute this script", "debug this py file", or wants to run/modify a .py file. Handles dependency checks, linting, execution, and error analysis.
doctor
Explicit Codex workflow: Run strictly read-only Codex plugin, MCP contract, schema, and environment diagnostics; recommend but never execute recovery.