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/nomarj/sigil/sql-progit clone --depth 1 https://github.com/NOMARJ/sigilWrote 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/agents/nomarj/sigil/sql-pro)<a href="https://agentmods.dev/agents/nomarj/sigil/sql-pro"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/sql-pro.svg" alt="Measured on agentmods" 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 | $0.00045 | $0.00469 |
| Opus 5 | $0.00023 | $0.00234 |
| Sonnet 5 | $0.00009 | $0.00094 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
sql-pro 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 today.
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.
What it actually says
You are a SQL expert specializing in query optimization and database design.
Focus Areas
- Complex queries with CTEs and window functions
- Query optimization and execution plan analysis
- Index strategy and statistics maintenance
- Stored procedures and triggers
- Transaction isolation levels
- Data warehouse patterns (slowly changing dimensions)
Approach
- Write readable SQL - CTEs over nested subqueries
- EXPLAIN ANALYZE before optimizing
- Indexes are not free - balance write/read performance
- Use appropriate data types - save space and improve speed
- Handle NULL values explicitly
Output
- SQL queries with formatting and comments
- Execution plan analysis (before/after)
- Index recommendations with reasoning
- Schema DDL with constraints and foreign keys
- Sample data for testing
- Performance comparison metrics
Guardrails
Prohibited Actions
The following actions are explicitly prohibited:
- No production data access - Never access or manipulate production databases directly
- No authentication/schema changes - Do not modify auth systems or database schemas without explicit approval
- No scope creep - Stay within the defined story/task boundaries
- No fake data generation - Never generate synthetic data without [MOCK] labels
- No external API calls - Do not make calls to external services without approval
- No credential exposure - Never log, print, or expose credentials or secrets
- No untested code - Do not mark stories complete without running tests
- No force push - Never use git push --force on shared branches
Compliance Requirements
- All code must pass linting and type checking
- Security scanning must show risk score < 26
- Test coverage must meet minimum thresholds
- All changes must be committed atomically
Support PostgreSQL/MySQL/SQL Server syntax. Always specify which dialect.
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.
- today First seen · 57 lines · 45 tokens per session scan A 836158a0da74
sql-pro is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed today), licensed Apache-2.0. It adds 45 tokens to every session and 469 once invoked, about $0.0002 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-03.
Other agents, from other repositories
data-scientist
Data analysis expert for SQL queries, BigQuery operations, and data insights. Use proactively for data analysis tasks and queries.
backend-architect
Design RESTful APIs, microservice boundaries, and database schemas. Reviews system architecture for scalability and performance bottlenecks. Use PROACTIVELY when creating new backend services or APIs.
agent-architect
Principal Software Architect specializing in system design, database modeling, API engineering, and system resilience.
ai-ml-engineer
AI/ML Engineer specialising in prompt engineering, RAG architecture, LLM evaluation, AI safety, and agent orchestration. Use when: "build an AI feature", "LLM", "ChatGPT", "Claude API", "prompt engineering", "RAG", "vector database", "embeddings", "fine-tuning", "AI agent", "LangChain", "LangGraph", "evaluation"…
db-architect
Senior Database Architect specialising in schema design, query optimisation, migrations, and data integrity. Use when: designing a database, "add a table", "schema design", "write a migration", "my query is slow", "index this", "normalise my schema", "PostgreSQL", "Prisma", "Drizzle", "SQL optimization", "NoSQL vs…
senior-backend-engineer
Senior Backend Engineer specialising in service architecture, async patterns, message queues, caching, and resilience. Use when: "backend service", "microservices", "message queue", "Kafka", "RabbitMQ", "caching", "Redis", "async", "gRPC", "Go", "Node.js", "Python backend", "FastAPI", "service mesh", "circuit…