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 jnPiyush/AgentX --skill pac-cligit clone --depth 1 https://github.com/jnPiyush/AgentXWrote 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/jnpiyush/agentx/pac-cli)<a href="https://agentmods.dev/skills/jnpiyush/agentx/pac-cli"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/pac-cli/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/jnpiyush/agentx/pac-cli"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/pac-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.01313 |
| Opus 5.5 | $0.00021 | $0.00525 |
| Sonnet 5.5 | $0.00011 | $0.00263 |
| Haiku 4.5 | $0.00005 | $0.00131 |
Grade A, and why
pac-cli 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 1mo 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Power Platform CLI (pac)
Purpose: provide the agent and the maker with exact
paccommands to validate, package, and import a generated solution. The builder agent never invokes destructive commands; it documents them for the maker.
When to Use
- After emitting an unpacked solution, validate
pac solution packsucceeds. - Generate the import script in the example README.
- Diagnose pack/import failures.
Installation
The maker installs once:
dotnet tool install --global Microsoft.PowerApps.CLI.Tool
Or via MSI from aka.ms/PowerPlatformCLI. Verify:
pac --version
Minimum supported version for this skill: 1.30.x (2025+).
Authentication
pac auth create --environment https://<env>.crm.dynamics.com --name agx-dev
pac auth select --name agx-dev
pac auth list
The builder agent MUST NOT call pac auth (no access to user credentials). The agent only documents the command in the generated README.
Core Commands (Solution Lifecycle)
| Command | Purpose | Safe from Agent? |
|---|---|---|
pac solution init --publisher-name agentx --publisher-prefix agx |
Bootstrap a new solution project | yes |
pac solution unpack --zipfile <file>.zip --folder ./src --packagetype Unmanaged |
Convert vendor-exported zip into source | yes (read-only) |
pac solution pack --zipfile build/solution.zip --folder ./src --packagetype Unmanaged |
Convert source into importable zip | yes (writes only to build/) |
pac solution check --path build/solution.zip |
Run Solution Checker static analysis | yes |
pac solution import --path build/solution.zip --async --publish-changes --activate-plugins |
Import zip into the current env | NO -- maker only |
pac solution export --name <UniqueName> --path build/exported.zip --managed false |
Export solution back to zip | NO -- maker only |
pac solution publish |
Publish customizations | NO -- maker only |
pac solution delete --solution-name <UniqueName> |
Delete a solution from the env | NO -- destructive |
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.
- 1mo ago Changed 8f7ac01dd821
- 1mo ago First seen · 130 lines · 53 tokens per session scan A 5e5a2c80fde7
pac-cli is a skill published in the GitHub repository jnPiyush/AgentX (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 53 tokens to every session and 1,313 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…