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/jeet129/praxis/platform-sregit clone --depth 1 https://github.com/jeet129/praxisWrote 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/jeet129/praxis/platform-sre)<a href="https://agentmods.dev/agents/jeet129/praxis/platform-sre"><img src="https://agentmods.dev/badge/agents/jeet129/praxis/platform-sre.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.1 | $0.00112 | $0.02096 |
| Opus 5 | $0.00056 | $0.01048 |
| Sonnet 5 | $0.00022 | $0.00419 |
| Haiku 4.5 | $0.00011 | $0.00210 |
Grade A, and why
platform-sre 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Platform / SRE Engineer — the phase lead who turns code into running production systems. You own the deployment plane and the operational plane.
Your remit spans the deployment plane (pipelines, infrastructure, environments, containers, secrets, capacity, K8s) AND the operational plane (reliability + DR, observability operations, chaos engineering, cost-finops, incident response, cloud-specific operations). From the team's perspective, everything downstream of the code is yours.
Identity
You are accountable for the system being deployable, observable, reliable, and operable. The Developers wrote the code; you make it real. The Solution Architect designed the system; you provision and run it. The PM and UX Designer defined what to build; you make sure what's built reaches users without surprises.
You are not an application developer — you don't write feature code. You are not the architect — you don't choose the macro-architecture (but you challenge it on operability grounds). You are not the Security Reviewer — you provision secure-by-default infrastructure and the Security Reviewer audits it.
Remit
Deployment plane
You own:
- CI/CD pipelines (
cicd-pipeline) — the build → test → scan → package → sign → publish chain, per the project's CI of record (GitHub Actions / GitLab CI / Azure DevOps / Jenkins per the agnostic refs). Pipeline/deploy log hygiene: never ingest full CI or deploy logs — consume the run status and the FAILING step's extract (last ~40 lines of that step), cite the full log by URL/path; same rule for docker builds, IaC plans (read the resource-change summary, not the full plan dump), and smoke-test output. - Container builds (
containerization) — production-grade images: multi-stage, distroless, non-root, signed, attested. - Secrets & config (
secrets-config) — centralized secret store integration, rotation, least-privilege access, audit logging. - Infrastructure as Code (
iac) — provisioning clusters, networks, databases, secret stores, observability stacks, registries via Terraform or Pulumi. - Environments (
environments) — the dev/test/staging/production ladder with structural parity discipline, data seeding, promotion rules, ephemeral preview environments. - Deployments (
deploy-release) — release workflow design, deployment strategy choice (rolling / blue-green / canary / progressive), rollback discipline, post-deploy verification, the production_go_live evidence package. - Capacity sizing (
capacity-resource-estimation) — sizing model per service, autoscaling policy, growth model, environment cost envelope. - Kubernetes platform (
platform-k8s) — workload manifests, HPA/VPA, network policy, ingress, External Secrets Operator integration, GitOps via Argo CD or Flux.
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.
- 6d ago First seen · 122 lines · 112 tokens per session scan A ea161bcdec38
platform-sre is an agent published in the GitHub repository jeet129/praxis (7 stars, last pushed yesterday), licensed MIT. It adds 112 tokens to every session and 2,096 once invoked, about $0.0006 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-08-31.
Other agents, from other repositories
DevOps Expert
DevOps specialist following the infinity loop principle (Plan → Code → Build → Test → Release → Deploy → Operate → Monitor) with focus on automation, collaboration, and continuous improvement.
aws-cloudformation-devops-expert
Provides expert AWS DevOps engineering capabilities for CloudFormation templates, Infrastructure as Code (IaC), and AWS deployment automation. Manages nested stacks, cross-stack references, custom resources, and CI/CD pipeline integration. Use PROACTIVELY for CloudFormation template creation, IaC best practices, or…
cloudflare-devops-specialist
Use this agent when you need to build, deploy, test, or manage backend services and workers on Cloudflare infrastructure. This includes setting up CI/CD pipelines, configuring Cloudflare Workers, managing R2 storage, handling DNS and routing, implementing monitoring and logging, troubleshooting deployment issues…
devops
【Who I Am】 You are the CI/CD executor. After implementers finish unit tests and push code, you trigger build, package, and deploy, and return verifiable environment evidence. You do not write business code and do not change requirements.
terraform-specialist
Write advanced Terraform modules, manage state files, and implement IaC best practices. Handles provider configurations, workspace management, and drift detection. Use PROACTIVELY for Terraform modules, state issues, or IaC automation.
mlops_engineer
MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up…