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 instructions/artisancloud/powerx/agents-mdgit clone --depth 1 https://github.com/ArtisanCloud/PowerXWrote 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/instructions/artisancloud/powerx/agents-md)<a href="https://agentmods.dev/instructions/artisancloud/powerx/agents-md"><img src="https://agentmods.dev/badge/instructions/artisancloud/powerx/agents-md.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 | $0.03835 | $0.03835 |
| Opus 5 | $0.01917 | $0.01917 |
| Sonnet 5 | $0.00767 | $0.00767 |
| Haiku 4.5 | $0.00383 | $0.00383 |
Grade A, and why
PowerX AGENTS.md scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Prometheus/Otel：启动 backend（`LOG_LEVEL=info make dev` 或目标环境），在脚本执行期间 `curl http://localhost:2112/metrics | grep powerx_capability_invoke_total`，确认 `powerx_capability_invoke_total`/`powerx_capability_invoke_error_total` How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PowerX Development Guidelines
Auto-generated from all feature plans. Last updated: 2025-11-05
Active Technologies
- Go 1.26.7（backend 单体，Buf toolchain） + Gin HTTP 栈、google.golang.org/grpc、Buf、GORM、Redis、PostgreSQL、EventBus、OpenTelemetry、px-plugin CLI (007-integration-gateway-and-mcp)
- PostgreSQL（CapabilityRecord, CapabilitySyncJob, InvocationTrace）、Redis（Capability cache、ToolStore、RateLimit、SelectorPolicySnapshot）、MinIO/S3（插件 workflow/composite 资产引用，仅存 URI） (007-integration-gateway-and-mcp)
- Go 1.26.7（backend），Node 20 + Nuxt 4（web-admin） + Gin HTTP 栈、gorilla/websocket、Pinia、Nuxt UI (012-websocket-docs-plan)
- PostgreSQL（ai_model_profiles/knowledge_*），Redis（现有队列/缓存） (012-websocket-docs-plan)
- Go 1.26.7（backend services），Node 20 + Nuxt 4（web-admin） + Gin HTTP、google.golang.org/grpc（Buf）、GORM、Redis、PostgreSQL、OpenTelemetry、Nuxt UI、Pinia (024-ai-engineering-skills)
- PostgreSQL（skills registry + execution trace + audit refs）、Redis（selector/cache/policy snapshot） (024-ai-engineering-skills)
- Go 1.26.7（backend services）、TypeScript/Nuxt 4（web-admin） + Gin HTTP、gRPC（Buf contracts）、GORM、PostgreSQL、Redis、Loki、Grafana、Promtail (025-powerx-docker-systemd)
- PostgreSQL（主数据）、Redis（缓存/队列）、MinIO/S3（备份与对象产物） (025-powerx-docker-systemd)
- Go 1.26.7（backend），TypeScript（Nuxt 4 / Vue 3，web-admin） + Gin HTTP、gRPC（Buf contracts）、GORM、Pinia、Nuxt UI (026-iam)
- PostgreSQL（IAM 用户/成员/角色数据）、Redis（会话与缓存） (026-iam)
- Go 1.26.7（backend）, TypeScript + Nuxt 4（web-admin） + Gin HTTP, GORM, PostgreSQL, Redis, systemd/ops scripts, Nuxt UI (027-monitor-center)
- PostgreSQL（策略/作业/演练/告警元数据）+ 文件或对象存储（备份产物） (027-monitor-center)
- Go 1.26.7 for backend/CoreX services and CLIs; TypeScript with Nuxt 4/Vue 3 for Web Admin; Buf toolchain for gRPC contracts. + Gin HTTP stack, GORM, PostgreSQL JSONB, Redis only if later used for read caches, google.golang.org/grpc, Buf, Pinia/Nuxt UI, existing PowerX capability registry and IAM/RBAC services. (029-metadata-governance)
- PostgreSQL tables for metadata definitions, tag bindings, references, audit events through existing audit infrastructure; seed YAML under
backend/config/metadata_governance. (029-metadata-governance)
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 · 102 lines · 3,835 tokens per session scan A 64b1112a33cc
PowerX AGENTS.md is an instructions file published in the GitHub repository ArtisanCloud/PowerX (364 stars, last pushed 3d ago), licensed Apache-2.0. It adds 3,835 tokens to every session, about $0.0192 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other instructions, from other repositories
scalar AGENTS.md
AGENTS.md instructions for scalar/scalar, covering agents.md - ai agent guide for scalar, project overview, prerequisites, first-time setup and commands.
she-love-me CLAUDE.md
Instructions for 863401402/she-love-me, covering claude.md and 唯一工作流.
real-estate-mcp CLAUDE.md
Instructions for tae0y/real-estate-mcp, covering claude.md, project overview, commands, run a single test file and run a single test by name.
md2wechat-skill AGENTS.md
AGENTS.md instructions for geekjourneyx/md2wechat-skill, covering agent 协作规范, working rules, anti-noise agent decision rules, discovery-first workflow and verification order.
md2wechat-skill CLAUDE.md
Claude Code instructions for geekjourneyx/md2wechat-skill, covering claude 工作指南, 项目概述, agent 发现优先, 版本发布流程 and 0. 真实环境 e2e 渲染验证（必须第一个执行）.
md2wechat-skill copilot-instructions.md
Copilot instructions for geekjourneyx/md2wechat-skill, covering copilot instructions — md2wechat, build, test, lint, build for current platform, run all tests (use gocache to avoid conflicts) and run a single package test.