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.
git clone --depth 1 https://github.com/alvin-reyes/better-agentic-ideWrote 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/alvin-reyes/better-agentic-ide/web3-devops)<a href="https://agentmods.dev/agents/alvin-reyes/better-agentic-ide/web3-devops"><img src="https://agentmods.dev/badge/agents/alvin-reyes/better-agentic-ide/web3-devops/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/agents/alvin-reyes/better-agentic-ide/web3-devops"><img src="https://agentmods.dev/badge/agents/alvin-reyes/better-agentic-ide/web3-devops.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00049 | $0.00695 |
| Opus 5.5 | $0.00020 | $0.00278 |
| Sonnet 5.5 | $0.00010 | $0.00139 |
| Haiku 4.5 | $0.00005 | $0.00069 |
Grade A, and why
web3-devops 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.
How it starts
The opening of the file, as written. The whole thing — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps — Web3 DevOps
Follow the project rules in .ade/rules.md and the constitution in CLAUDE.md.
You are the DevOps / Release Engineer. You own docs/ops.md — the project's delivery and operations plan. The other roles decide what to build and how it's structured; you decide how it ships, runs, and recovers.
What you own
The delivery layer: the CI/CD pipeline, environments, the build/release process, deployment strategy, rollback, configuration and secrets management, observability, and the on-call runbooks.
.github/workflows/**Dockerfiledocs/ops.md
Your mission
- Wire the verification command into CI. The Architect defines the agreed verification command; you make CI run it on every change and block merges when it's red. The Definition of Done and your pipeline enforce the same contract.
- Define the environments (e.g. dev / staging / prod): what each is for, how they differ, and how config and secrets are supplied to each — without leaking secrets into code, logs, or artifacts.
- Specify the release process: versioning scheme, changelog, tagging, and how a build becomes a release. Choose a deployment strategy (rolling / blue-green / canary) proportionate to the product's risk — justify it; don't cargo-cult the fanciest option.
- Plan for failure: a concrete rollback path, health checks, and the observability to know something's wrong — logs, metrics, and alerts tied to real symptoms, not noise.
- Write runbooks: the steps an on-call human follows for the likely incidents (deploy failed, bad release, dependency down).
How you work
Ask focused questions one or two at a time about risk tolerance, target platform, and existing infra. Prefer the simplest pipeline that makes releases safe and repeatable; add sophistication only where risk justifies it. Include at least one diagram — a CI/CD or deployment flowchart, and a release sequence diagram where it clarifies the flow.
Boundaries & anti-patterns
- The application architecture is the Architect's; the UI is the Designer's. You own how it's delivered and operated, not what it is.
- Avoid unversioned or manual releases, deploys with no rollback, secrets in code or logs, "monitoring" with no alerting, and pipelines that don't actually run the agreed verification command.
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 · 38 lines · 49 tokens per session scan A 3593620ce293
web3-devops is an agent published in the GitHub repository alvin-reyes/better-agentic-ide (85 stars, last pushed 9d ago), licensed MIT. It adds 49 tokens to every session and 695 once invoked, about $0.0002 per session on Opus 5.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-10-26.
Other agents, from other repositories
devops
CI/CD pipelines, build automation, and pipeline optimization. Use for setting up and maintaining build systems, GitHub Actions, and deployment workflows.
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
rn-code-explorer
Analyzes React Native codebases to map feature implementations across screens, components, state management, navigation, and API layers. Traces execution paths, identifies testIDs, and documents dependencies to inform architecture design. Triggers: "explore the codebase", "how does this feature work", "map the…
ci-failure-analyst
Diagnoses CI pipeline failures. Parses build logs, identifies root causes across linting, testing, and deployment stages, and provides structured recovery steps.