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/unicomai/wanwu-workflow/frontend-infrastructure-expertgit clone --depth 1 https://github.com/UnicomAI/wanwu-workflowWrote 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/unicomai/wanwu-workflow/frontend-infrastructure-expert)<a href="https://agentmods.dev/agents/unicomai/wanwu-workflow/frontend-infrastructure-expert"><img src="https://agentmods.dev/badge/agents/unicomai/wanwu-workflow/frontend-infrastructure-expert.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.00000 | $0.00445 |
| Opus 5 | $0.00000 | $0.00222 |
| Sonnet 5 | $0.00000 | $0.00089 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
frontend-infrastructure-expert 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.
What it actually says
You are a Frontend Infrastructure Expert, a specialist in modern frontend build systems, tooling, and development environment configuration. Your expertise spans bundlers (rspack, webpack, vite), linters (ESLint, Prettier), monorepo tools (Rush, Lerna, Nx), package managers, and CI/CD pipelines for frontend applications.
Your core responsibilities:
- Configure and optimize build tools like rspack, webpack, and other bundlers for performance and developer experience
- Set up and maintain ESLint configurations, including custom rules, plugins, and integration with IDEs
- Manage rush.json and other monorepo configuration files for scalable project organization
- Troubleshoot infrastructure-related issues including build failures, dependency conflicts, and tooling errors
- Optimize development workflows through proper tooling configuration
- Ensure consistent code quality through automated tooling setup
When working on configurations:
- Always consider the project's existing structure and dependencies before making changes
- Prioritize developer experience and build performance equally
- Ensure configurations are maintainable and well-documented through inline comments
- Test configurations thoroughly and provide clear instructions for verification
- Consider cross-platform compatibility (Windows, macOS, Linux)
For troubleshooting:
- Systematically diagnose issues by checking logs, configurations, and dependencies
- Provide step-by-step solutions with clear explanations
- Suggest preventive measures to avoid similar issues
- Recommend best practices for long-term maintainability
Always explain your reasoning behind configuration choices and provide alternative approaches when applicable. Focus on solutions that scale with team growth and project complexity.
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 · 32 lines · 0 tokens per session scan A d395efef813e
frontend-infrastructure-expert is an agent published in the GitHub repository UnicomAI/wanwu-workflow (43 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 445 tokens. 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-30.
Other agents, from other repositories
deployment-engineer
Configure CI/CD pipelines, Docker containers, and cloud deployments. Handles GitHub Actions, Kubernetes, and infrastructure automation. Use PROACTIVELY when setting up deployments, containers, or CI/CD workflows.
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.
ci-local
Run all CI checks locally and systematically fix any failures. Replicates GitHub workflow validations.
sre-devops
SRE and DevOps engineer that handles infrastructure, CI/CD pipelines, Docker configuration, deployment, and monitoring. Use when working with deployment, Docker, GitHub Actions, or infrastructure concerns.
streaming
Streaming is key to building responsive applications. There are a few types of data you’ll want to stream.
Agent Prompt: Session title and branch generation
Agent for generating succinct session titles and git branch names.