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/pengguogo/ai-coding-skillsWrote 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/pengguogo/ai-coding-skills/ops-executor)<a href="https://agentmods.dev/agents/pengguogo/ai-coding-skills/ops-executor"><img src="https://agentmods.dev/badge/agents/pengguogo/ai-coding-skills/ops-executor/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/pengguogo/ai-coding-skills/ops-executor"><img src="https://agentmods.dev/badge/agents/pengguogo/ai-coding-skills/ops-executor.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.00091 | $0.01244 |
| Opus 5.5 | $0.00036 | $0.00498 |
| Sonnet 5.5 | $0.00018 | $0.00249 |
| Haiku 4.5 | $0.00009 | $0.00124 |
Grade C, and why
ops-executor scanned grade C with 1 finding 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 26d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
1. **不删除目录**：不执行 `rm -rf`、`rmdir` 或等效操作 The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 26d ago First seen · 98 lines · 91 tokens per session scan C 214deba75745
ops-executor is an agent published in the GitHub repository pengguogo/ai-coding-skills (2 stars, last pushed 26d ago), with no licence file. It adds 91 tokens to every session and 1,244 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-21.
Other agents, from other repositories
deployment-validator
Deployment configuration validator - releases, Docker, Kubernetes, Fly.io. Use proactively before deploying to production.
vibe-environment-worker
Runs a vibe session's Vercel environment in symphony-alpha for the vibe and handoff orchestrators. Create mode takes the production flag snapshot in PostHog for the person's real account, pushes the vibe/ branch, starts the environment through the repo's request workflow, follows it to the end, and records the app…
dc-deployer
Use this agent for the release phase of a dev-crew run, only after qa returns an overall PASS. Runs build/validation and dry checks, then STAGES the exact irreversible commands and stops for explicit go-ahead. Never auto-executes a deploy.
ops-deploy
Secure deployment with pre-deploy checklist. Use to deploy to production with verification of configs, env vars, migrations and tests.
platform
Use for everything that happens after the merge: releases and versioning, deploys and CI/CD, cloud infrastructure, environments, SLOs, error budgets, observability, performance budgets, 'production is slow', 'the deploy failed', 'I want to ship the version'. One door for shipping and running the product.
GitopsGeezer
GitOps and ArgoCD expert. Use for ArgoCD setup, ApplicationSets, multi-cluster deployments, repository structure, and GitOps best practices.