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.
/plugin marketplace add davepoon/buildwithclaudenpx agentmods add plugins/davepoon/buildwithclaude/agents-infrastructure-operationsgit clone --depth 1 https://github.com/davepoon/buildwithclaudeWrote 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/plugins/davepoon/buildwithclaude/agents-infrastructure-operations)<a href="https://agentmods.dev/plugins/davepoon/buildwithclaude/agents-infrastructure-operations"><img src="https://agentmods.dev/badge/plugins/davepoon/buildwithclaude/agents-infrastructure-operations.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
agents-infrastructure-operations 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
{
"name": "agents-infrastructure-operations",
"version": "1.0.0",
"description": "Agents for cloud infrastructure, DevOps, and database operations",
"author": {
"name": "BuildWithClaude Community",
"url": "https://github.com/davepoon/buildwithclaude"
},
"repository": "https://github.com/davepoon/buildwithclaude",
"license": "MIT",
"keywords": [
"agents",
"subagents",
"infrastructure-operations",
"cloud-architect",
"database-admin",
"database-optimization",
"database-optimizer",
"deployment-engineer",
"devops-troubleshooter",
"network-engineer",
"terraform-specialist"
]
}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 · 24 lines scan A c040d5f858ee
agents-infrastructure-operations is a plugin published in the GitHub repository davepoon/buildwithclaude (3,405 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
api-pagination
Implements efficient API pagination using offset, cursor, and keyset strategies for large datasets. Use when building paginated endpoints, implementing infinite scroll, or optimizing database queries for collections.
api-rate-limiting
Implements API rate limiting using token bucket, sliding window, and Redis-based algorithms to protect against abuse. Use when securing public APIs, implementing tiered access, or preventing denial-of-service attacks.
backend-architect
Use this agent when designing APIs, building server-side logic, implementing databases, or architecting scalable backend systems. This agent specializes in creating robust, secure, and performant backend services. Examples:\n\n \nContext: Designing a new API\nuser: "We need an API for our social sharing feature.
mongodb-atlas-checker
Verify MongoDB Atlas setup and configuration for backend applications. Checks connection strings, environment variables, connection pooling, and ensures proper setup for Next.js and NestJS applications. Use when verifying MongoDB Atlas setup, checking connection strings or environment variables, or troubleshooting…
mongodb-migration-expert
Database schema design, indexing, and migration guidance for MongoDB-based applications. Use when adding or changing MongoDB collections, indexes, or fields, designing schema for multi-tenant or large datasets, or planning forward-only migrations.
performance-expert
Backend, database, and infrastructure performance expert covering API response times, query and index optimization, N+1 elimination, caching and background jobs, server profiling, and build/asset delivery. Use when improving API latency, optimizing database queries or indexes, designing a caching layer, moving heavy…