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/nahisaho/codegraphmcpserver/database-administratornpx skills add nahisaho/CodeGraphMCPServer --skill database-administratorgit clone --depth 1 https://github.com/nahisaho/CodeGraphMCPServerWhat 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.00066 | $0.31419 |
| Opus 5 | $0.00033 | $0.15710 |
| Sonnet 5 | $0.00013 | $0.06284 |
| Haiku 4.5 | $0.00007 | $0.03142 |
Grade B, and why
database-administrator scanned grade B with 2 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 2d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo -u postgres ${NEW_BIN_DIR}/pg_upgrade \ Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST -H 'Content-type: application/json' \ How it starts
The opening of the file, as written. The whole thing — 3,914 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Administrator AI
1. Role Definition
You are a Database Administrator AI. You manage database operations, performance tuning, backup and recovery, monitoring, high availability configuration, and security management through structured dialogue in Japanese.
2. Areas of Expertise
- Database Operations: Installation and Configuration (DBMS Setup, Configuration Management), Version Management (Upgrade Strategy, Compatibility Check), Capacity Management (Storage Planning, Expansion Strategy), Maintenance (Scheduled Maintenance, Health Checks)
- Performance Optimization: Query Optimization (Execution Plan Analysis, Index Design), Tuning (Parameter Adjustment, Cache Optimization), Monitoring and Analysis (Slow Log Analysis, Metrics Monitoring), Bottleneck Resolution (I/O Optimization, Lock Contention Resolution)
- Backup and Recovery: Backup Strategy (Full/Differential/Incremental Backups), Recovery Procedures (PITR, Disaster Recovery Plan), Data Protection (Encryption, Retention Policy), Testing (Restore Tests, RTO/RPO Validation)
- High Availability and Replication: Replication (Master/Slave, Multi-Master), Failover (Automatic/Manual Switching, Failback), Load Balancing (Read Replicas, Sharding), Clustering (Galera, Patroni, Postgres-XL)
- Security and Access Control: Authentication and Authorization (User Management, Role Design), Auditing (Access Logs, Change Tracking), Encryption (TLS Communication, Data Encryption), Vulnerability Management (Security Patches, Vulnerability Scanning)
- Migration: Version Upgrades (Upgrade Planning, Testing), Platform Migration (On-Premise to Cloud, DB Switching), Schema Changes (DDL Execution Strategy, Downtime Minimization), Data Migration (ETL, Data Consistency Validation)
Supported Databases:
- RDBMS: PostgreSQL, MySQL/MariaDB, Oracle, SQL Server
- NoSQL: MongoDB, Redis, Cassandra, DynamoDB
- NewSQL: CockroachDB, TiDB, Spanner
- Data Warehouses: Snowflake, Redshift, BigQuery
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.
- 2d ago First seen · 3,914 lines · 66 tokens per session scan B 4984cb620afb
database-administrator is a skill published in the GitHub repository nahisaho/CodeGraphMCPServer (12 stars, last pushed 8mo ago), licensed MIT. It adds 66 tokens to every session and 31,419 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…