assembly-agent

assembly-agent is an agent for coding agents from ToluVictor/canvas-apps-tools. It costs 0 tokens per session (3,802 once invoked), scanned A, original, MIT.

An assembler for Microsoft Power Apps Canvas App YAML. It combines the app’s control tree with separate layout, control, and styling annotation files, then checks and fixes assembly errors before saving the result.

In plain words
What is it for?
Use it to assemble a complete Canvas App YAML file from a skeleton and specialist annotations, with optional data-binding and paste-target settings.
Why use it?
It removes the manual work of merging separate app decisions into one complete YAML file and catches errors in the combined output.

Agent

Part of the canvas-apps-tools plugin — 1 skill, 5 agents shipped together

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.

agentmods
npx agentmods add agents/toluvictor/canvas-apps-tools/assembly-agent
Clone the repo
git clone --depth 1 https://github.com/ToluVictor/canvas-apps-tools

Or install canvas-apps-tools, the plugin that ships this one along with the rest of its 1 skill, 5 agents.

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.

agentmods badge for assembly-agent

README.md
[![agentmods](https://agentmods.dev/badge/agents/toluvictor/canvas-apps-tools/assembly-agent.svg)](https://agentmods.dev/agents/toluvictor/canvas-apps-tools/assembly-agent)
Your own site
<a href="https://agentmods.dev/agents/toluvictor/canvas-apps-tools/assembly-agent"><img src="https://agentmods.dev/badge/agents/toluvictor/canvas-apps-tools/assembly-agent.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,802 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.03802
Opus 5 $0.00000 $0.01901
Sonnet 5 $0.00000 $0.00760
Haiku 4.5 $0.00000 $0.00380

Measured 5d ago against content hash d6bd3d3cf46c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

assembly-agent 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 5d 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.

skills/canvas-apps-ui-gen/agents/assembly-agent.md · 325 lines

How it starts

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

Assembly + QA Agent

You are a Power Apps Canvas App YAML assembler and quality assurance checker. Your job is to:

  1. Merge three annotation files (layout, controls, styling) with a structural skeleton into a single complete YAML file
  2. Self-validate the assembled YAML against all QA rules
  3. Fix any issues found inline before writing the output file

You need no reference docs for assembly — all decisions have already been made by the specialist agents. For QA, you will read Section C of reference/controls-reference.md and temp-design-spec.md as part of your checks.


Your Inputs

You will be given:

  1. Path to temp-skeleton.md — the structural control tree (control names, types, nesting hierarchy, paste target)
  2. Path to temp-layout-annotations.yaml — layout and sizing properties per control
  3. Path to temp-controls-annotations.yaml — control types and semantic properties per control
  4. Path to temp-styling-annotations.yaml — visual styling properties per control
  5. Path to temp-design-spec.md — used for QA fidelity checks
  6. Paste target (a, b, or c) and screen name — determines the root element format
  7. Data binding info — whether ClearCollect goes inline (new screen) or as a separate block
  8. Output file path — write the complete assembled YAML here
  9. Skill directory path — used to read reference/controls-reference.md Section C for QA

Read all annotation files and the design spec before writing any output.


Assembly Algorithm

Step 0 — Determine Root Format (do this FIRST, before any assembly)

Read the Paste target: line from temp-skeleton.md. This determines the entire file structure — do not skip this step.

  • Paste target (b) — new screen: The output file MUST start with Screens:. Never start with - screenRoot:.
    Screens:
      ScreenName:
        Properties:
          Fill: =RGBA(249,250,251,1)
          OnVisible: |-
            =ClearCollect(colSampleData, ...)
        Children:
          - screenRoot:
              Control: [email protected]
              ...
    

Read the full file on GitHub · 325 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.

  1. 5d ago First seen · 325 lines · 0 tokens per session scan A d6bd3d3cf46c

Subscribe to this mod's changes

assembly-agent is an agent published in the GitHub repository ToluVictor/canvas-apps-tools (135 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,802 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.

Related

Other agents, from other repositories

screen-builder

Use when an orchestrator needs ONE screen of a Power Apps mobile app implemented from a per-screen spec in native-app-plan.md. Designed to run in parallel with sibling screen-builder instances — each builder sees only its assigned screen. Called by /create-mobile-app and /edit-app; not invoked directly by users.

microsoft/power-platform-skills · 65 tokens

screen-planner

Use when an orchestrator needs a screen graph + per-screen specs (navigation pattern, components, data, native capabilities) and a plan-time HTML preview or screen-plan delta for a Power Apps mobile app. Read-only — does NOT write TSX. Called by native-app-planner and /edit-app; not invoked directly by users.

microsoft/power-platform-skills · 71 tokens

native-app-planner

Use when the orchestrator needs a full plan + four approval gates (data model → native capabilities → connectors → screens) for a Power Apps mobile app. Read-only — proposes everything, mutates nothing. Called by /create-mobile-app; not invoked directly by users.

microsoft/power-platform-skills · 59 tokens

ai-webapi-integration

Use this agent when the user needs to integrate one of the Power Pages generative-AI summarization APIs into their frontend code. The agent supports two APIs: 1. Search Summary — POST /api/search/v1.0/summary 2. Data Summarization — POST /api/summarization/data/v1.0/ ( )?$select=...&$expand=... Data Summarization can…

microsoft/power-platform-skills · 309 tokens

data-model-architect

Use when an orchestrator needs a Dataverse data model proposed (existing-table reuse, new tables in dependency-tier order, Mermaid ER diagram) for embedding in native-app-plan.md. Read-only — proposes, never mutates. Called by native-app-planner and /edit-app; not invoked directly by users.

microsoft/power-platform-skills · 67 tokens

webapi-integration

Use this agent when the user needs to integrate Power Pages Web API for a specific Dataverse table into their frontend code. Trigger examples: "integrate web api for products table", "add api calls for orders", "connect my site to the blog posts table", "implement crud for categories", "set up web api client", "create…

microsoft/power-platform-skills · 182 tokens