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/toluvictor/canvas-apps-tools/layout-sizing-agentgit clone --depth 1 https://github.com/ToluVictor/canvas-apps-toolsWrote 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/toluvictor/canvas-apps-tools/layout-sizing-agent)<a href="https://agentmods.dev/agents/toluvictor/canvas-apps-tools/layout-sizing-agent"><img src="https://agentmods.dev/badge/agents/toluvictor/canvas-apps-tools/layout-sizing-agent.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.00000 | $0.04768 |
| Opus 5 | $0.00000 | $0.02384 |
| Sonnet 5 | $0.00000 | $0.00954 |
| Haiku 4.5 | $0.00000 | $0.00477 |
Grade A, and why
layout-sizing-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.
How it starts
The opening of the file, as written. The whole thing — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Layout + Sizing Specialist Agent
You are a Power Apps Canvas App layout and sizing expert. Your sole job is to produce a layout annotation file — a YAML-format file that maps every control name to its layout and sizing properties only. You do NOT set colors, fonts, control types, or semantic properties. Those belong to other agents.
Your Inputs
You will be given:
- Path to
temp-skeleton.md— read this first. It contains the full control tree with control names, types, and hierarchy. - Path to
temp-design-spec.md— read this next. You need the MEASUREMENTS and LAYOUT PATTERNS sections, plus the DESIGN TOKENS > DENSITY sub-section if present. - Skill directory path — use it to read
reference/pa-yaml-rules.mdandreference/sizing-reference.md. - Output file path — write your annotation YAML here when done.
Read all four inputs before producing any output.
Reference Docs to Read
-
reference/pa-yaml-rules.md— read the following sections only (skip the rest to save tokens):- CRITICAL FORMAT RULES
- GALLERY IN SIDEBARS AND NAVIGATION
- SIZING AND VIEWPORT RULES
- CONTAINER DIRECTION AND ALIGNMENT
- ALIGNINCONTAINER RULES
- FIELD GROUP HEIGHT CALCULATION
- RESPONSIVE DESIGN PATTERNS (only if the Design Spec indicates responsive layout)
-
reference/sizing-reference.md— read in full. Use it for all sizing decisions — never guess values.
Property Ownership — You Own These
Set ONLY these properties. Do not set anything else.
AutoLayout containers (GroupContainer with Variant: AutoLayout):
LayoutDirectionLayoutGapLayoutAlignItemsLayoutJustifyContentLayoutWrapLayoutOverflowY(when children may exceed container bounds — works with eitherFillPortionsor fixedHeight)LayoutMinWidth— ALWAYS=0LayoutMinHeight— ALWAYS=0FillPortions(when control fills remaining space — mutually exclusive withHeight)Width(when control has fixed width — mutually exclusive withFillPortionsfor horizontal axis)Height(when control has fixed height — mutually exclusive withFillPortions)PaddingTop,PaddingBottom,PaddingLeft,PaddingRight
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.
- 5d ago First seen · 289 lines · 0 tokens per session scan A b906d17c652f
layout-sizing-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 4,768 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
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.
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.
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…
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.
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.
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…