What is solution-anatomy?

A file structure for an unpacked Microsoft Power Platform solution. It organizes apps, tables, flows, security, relationships, and package settings so the solution can be checked, compared, packed, and imported.

Use it to create or review solution folders, publishers, versioning, dependencies, managed or unmanaged packages, and component registrations.

It prevents platform components from becoming an unstructured export that is difficult to review or maintain. It also helps solutions move between environments with their dependencies understood.

solution-anatomy — Skill for Claude Code and Codex by jnPiyush/AgentX

Install

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.

Any agent

npx skills add jnPiyush/AgentX --skill solution-anatomy

Clone the repo

git clone --depth 1 https://github.com/jnPiyush/AgentX

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jnpiyush/agentx/solution-anatomy/github.svg)](https://agentmods.dev/skills/jnpiyush/agentx/solution-anatomy)

Your own site

<a href="https://agentmods.dev/skills/jnpiyush/agentx/solution-anatomy"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/solution-anatomy/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jnpiyush/agentx/solution-anatomy"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/solution-anatomy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,831 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00065	$0.01831
Opus 5.5	$0.00026	$0.00732
Sonnet 5.5	$0.00013	$0.00366
Haiku 4.5	$0.00006	$0.00183

Measured 1mo ago against content hash 6cc1cd52af03, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

solution-anatomy 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.

.github/skills/low-code/solution-anatomy/SKILL.md · 171 lines

How it starts

The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Power Platform Solution Anatomy

Purpose: let an agent emit a deterministic source tree that round-trips through pac solution unpack / pac solution pack and imports cleanly into a Dataverse environment.

When to Use

Generating a new Power Platform solution from a PRD
Adding a component (table, flow, app, agent) to an existing unpacked solution
Reviewing a solution before packaging or import
Diffing two solutions semantically (per-component, not raw XML)

The On-Disk Layout (Canonical)

<solution-root>/
  src/
    Other/
      Solution.xml            # manifest: UniqueName, Version, Publisher, Managed flag, RootComponents
      Customizations.xml      # global customizations (option sets, security roles, sitemap)
      Relationships.xml       # cross-entity relationships
    Entities/
      <prefix>_<entityname>/  # one folder per Dataverse table
        Entity.xml
        FormXml/
        SavedQueries/
        Views/
    CanvasApps/
      <prefix>_<appname>_<DocumentUri>/
        CanvasManifest.json
        Src/                  # *.fx.yaml files (Power Fx source)
        Assets/
    Workflows/
      <prefix>_<name>-FLOW.json   # Power Automate cloud flow
    Bots/
      <prefix>_<botname>/         # Copilot Studio agent
        bot.yaml
        topics/*.yaml
        knowledge/*.yaml
    Roles/                    # security roles
    WebResources/             # static assets, JS, images
    OptionSets/               # global choice columns
    ConnectionReferences/     # named connection bindings
    EnvironmentVariables/     # config that varies by environment

All folders are optional except src/Other/Solution.xml and src/Other/Customizations.xml.

Solution.xml -- Required Fields

Field	Rule
`UniqueName`	Lowercase, alphanumeric, underscores. Must be globally unique within the tenant. Convention: `<publisherprefix>_<short_solution_name>`.
`LocalizedName`	Display name shown in maker portal.
`Description`	One-paragraph summary.
`Version`	Four-part SemVer-ish `MAJOR.MINOR.BUILD.REVISION`. Bump `BUILD` per build, `REVISION` per hotfix.
`Managed`	`0` for unmanaged source (the only form pac solution pack should produce from this tree).
`Publisher`	Inline element with `UniqueName`, `LocalizedNames`, `CustomizationPrefix`, `CustomizationOptionValuePrefix`.
`RootComponents`	One `<RootComponent>` per included component, with `type` and `schemaName`.
`MissingDependencies`	Empty unless the solution layers on another solution.

Read the full file on GitHub · 171 lines

Changes

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 6cc1cd52af03
1mo ago First seen · 171 lines · 65 tokens per session scan A 17a1415837fa

Subscribe to this mod's changes

solution-anatomy is a skill published in the GitHub repository jnPiyush/AgentX (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 65 tokens to every session and 1,831 once invoked, about $0.0003 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.

DevOps and cloud

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens