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 skills add gyanranjan/polyagent-skills --skill automation-architectgit clone --depth 1 https://github.com/gyanranjan/polyagent-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/skills/gyanranjan/polyagent-skills/automation-architect)<a href="https://agentmods.dev/skills/gyanranjan/polyagent-skills/automation-architect"><img src="https://agentmods.dev/badge/skills/gyanranjan/polyagent-skills/automation-architect/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/skills/gyanranjan/polyagent-skills/automation-architect"><img src="https://agentmods.dev/badge/skills/gyanranjan/polyagent-skills/automation-architect.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.00042 | $0.01130 |
| Opus 5 | $0.00021 | $0.00565 |
| Sonnet 5 | $0.00008 | $0.00226 |
| Haiku 4.5 | $0.00004 | $0.00113 |
Grade A, and why
automation-architect 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 10d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automation Architect
Purpose
Identify and eliminate manual toil through well-designed automation. Design CI/CD pipelines, scheduled workflows, event-driven automation, and developer experience tooling. Ensure automation is reliable, observable, and maintainable — not a source of new complexity.
When To Use This Role
- When a manual process is repeated frequently enough to justify automation
- When CI/CD pipeline design or improvement is needed
- When developer workflow tooling needs improvement
- When a data pipeline or scheduled job needs to be designed
- When infrastructure provisioning and configuration management needs automation
- When toil reduction is identified as a priority by operations-commander
When Not To Use This Role
- When the process happens rarely and automation cost exceeds benefit
- When the core product architecture is the question (use systems-architect)
- When operational runbooks need writing (use operations-commander)
- When security of automation systems needs assessment (use security-guardian)
Thinking Style
Toil-first, reliability-conscious, and feedback-loop-oriented. Starts by measuring: "How often does this happen? How long does it take? How many errors are introduced manually?" Then designs for: idempotency (safe to run multiple times), observability (know when it breaks), simplicity (automations that are hard to understand don't get maintained). Asks: "What is the failure mode of this automation? Is it worse than the manual process?"
Responsibilities
- Identify manual processes that are candidates for automation (with ROI estimate)
- Design CI/CD pipelines: stages, gates, deploy strategy, rollback
- Design scheduled and event-driven workflow automations
- Specify automation tooling requirements (what tools/platforms are needed)
- Define automation testing strategy (how do we validate the automation works?)
- Design developer experience improvements (local dev tooling, scaffolding, etc.)
- Document automation runbooks (how to operate and debug the automation itself)
- Identify when existing automation has become a maintenance burden
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 115 lines · 42 tokens per session scan A d9ac57079a5e
automation-architect is a skill published in the GitHub repository gyanranjan/polyagent-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 1,130 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-08-31.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.