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 VincentChuWaiChow/vanguard-frontier-agentic --skill aws-rds-aurora-performance-investigatorgit clone --depth 1 https://github.com/VincentChuWaiChow/vanguard-frontier-agenticWrote 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/vincentchuwaichow/vanguard-frontier-agentic/aws-rds-aurora-performance-investigator)<a href="https://agentmods.dev/skills/vincentchuwaichow/vanguard-frontier-agentic/aws-rds-aurora-performance-investigator"><img src="https://agentmods.dev/badge/skills/vincentchuwaichow/vanguard-frontier-agentic/aws-rds-aurora-performance-investigator/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/vincentchuwaichow/vanguard-frontier-agentic/aws-rds-aurora-performance-investigator"><img src="https://agentmods.dev/badge/skills/vincentchuwaichow/vanguard-frontier-agentic/aws-rds-aurora-performance-investigator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00070 | $0.00585 |
| Opus 5 | $0.00035 | $0.00293 |
| Sonnet 5 | $0.00014 | $0.00117 |
| Haiku 4.5 | $0.00007 | $0.00059 |
Grade A, and why
aws-rds-aurora-performance-investigator 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 8d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS RDS Aurora Performance Investigator
Purpose
Act as the RDS/Aurora performance investigator who refuses to resize first and ask questions later.
When to use
Use this skill for:
- RDS or Aurora latency, connection errors, query timeouts, slow reads/writes, or replica lag
- Performance Insights, DB load, wait events, top SQL, deadlocks, storage, CPU, memory, or I/O investigation
- database incident RCA, failover readiness, maintenance event review, or read-replica behavior analysis
- application connection-pool or transaction behavior suspected of causing database pressure
Lean operating rules
- Prefer current AWS documentation tools for service behavior. Use the per-skill facts and sampled live evidence in
references/official-sources.md; when the user has configured read-only AWS MCP access, use exposed read-only tools for current-state evidence instead of guessing. - Separate confirmed facts from inference. If state was not queried or shown, say so.
- Challenge broad access, public exposure, destructive automation, untested recovery, hidden cost, and vague production claims.
- Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
- Load references only when needed; do not pull all deep guidance into short answers.
References
Load these only when needed:
- Workflow and output contract — use when executing the full review, incident triage, implementation guidance, or formatting the final answer.
- Safety checklist — use before privileged, destructive, traffic-changing, cost-changing, compliance-impacting, or production-impacting recommendations.
- Official sources — use when grounding AWS service behavior or checking the detailed source list.
- RDS and Aurora Performance Evidence Guide — use for domain-specific failure modes, safe workflow, verification targets, and pushback criteria.
What ships with it
5 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.
- 8d ago First seen · 53 lines · 70 tokens per session scan A fff5ff630966
aws-rds-aurora-performance-investigator is a skill published in the GitHub repository VincentChuWaiChow/vanguard-frontier-agentic (22 stars, last pushed today), licensed Apache-2.0. It adds 70 tokens to every session and 585 once invoked, about $0.0003 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-09-04.
Other skills, from other repositories
senior-engineering-partner
A strict code reviewer, pair programmer, debugger, and mentor for Python, Bash, Google Apps Script, JavaScript, and Swift/Apple platforms. Use when writing, reviewing, debugging, planning, or securing code, or for senior-level rigor, a security review, or mentoring. Mode triggers — REVIEW: (critique + refactor)…
r-data
R data manipulation, formats, and database packages. Use for data wrangling with dplyr/data.table, reading files (CSV, Excel, JSON, Arrow), and database connections (SQL, MongoDB, Redis).
r-data-database
R database packages for SQL and NoSQL. Use for DBI connections, SQL queries, dbplyr, SQLite, PostgreSQL, MySQL, MongoDB, Redis.
lintr
R lintr package for static code analysis. Use for checking R code style and finding potential issues.
logging
R logging package for Python-style logging. Use for logging with handlers and formatters.
DBI
R DBI package for database interface. Use for connecting to and querying databases with a common interface.