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 agents/pgedge/pgedge-postgres-mcp/testing-framework-architectgit clone --depth 1 https://github.com/pgEdge/pgedge-postgres-mcpWhat 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.02259 |
| Opus 5 | $0.00000 | $0.01130 |
| Sonnet 5 | $0.00000 | $0.00452 |
| Haiku 4.5 | $0.00000 | $0.00226 |
Grade A, and why
testing-framework-architect 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.
The source is not reproduced here
Licensed PostgreSQL
The repository is licensed PostgreSQL, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 166 lines · 0 tokens per session scan A b5a3b89b67e1
testing-framework-architect is an agent published in the GitHub repository pgEdge/pgedge-postgres-mcp (221 stars, last pushed 7d ago), licensed PostgreSQL. It costs nothing until one of its globs matches a file; then it loads 2,259 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 agents, from other repositories
database-engineer
PostgreSQL specialist: schema design, migrations, query optimization, pgvector/full-text search, Alembic migrations.
db-postgres-expert
Use this agent when you need expert PostgreSQL database management, optimization, and architecture guidance. This agent specializes in PostgreSQL 16+ features, advanced SQL queries, indexing strategies, performance tuning, replication, and high-availability configurations. Examples: Context: User needs to optimize…
postgres-expert
Use this agent when the user needs expert guidance on PostgreSQL database administration, configuration, or troubleshooting. Examples include:\n\n- User: "What are the key performance metrics I should monitor on my PostgreSQL 15 production server?"\n Assistant: "Let me use the postgres-expert agent to provide…
database-analyst
Use for complex database analysis, optimization recommendations, schema design review, data quality assessment, and multi-step data exploration tasks.
database-attacker
Delegates to this agent when the user wants database-specific offensive testing on an authorized target — SQL and NoSQL injection depth, authenticated database enumeration, DBMS privilege escalation, and safe data-extraction validation across MySQL, PostgreSQL, MSSQL, Oracle, MongoDB, and Redis. Executes with…
database-performance-reviewer
Database performance and scaling reviewer for World of ClaudeCraft (Postgres via pg). Use on any change that touches SQL, a database call site, schema or indexes, query cadence or cardinality, pool or lock behavior, timeout policy, scheduled/background database work, database driver or PostgreSQL…