controls-agent

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

A specialist that creates a YAML file describing each control in a Power Apps Canvas App, including its type, variant, and functional meaning. It uses a control tree and design specification as input.

In plain words
What is it for?
It helps document buttons, fields, navigation items, and other app controls for later design or implementation work.
Why use it?
It separates what controls do from how they look, so control details do not get mixed with layout, colors, fonts, or spacing.

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/controls-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 controls-agent

README.md
[![agentmods](https://agentmods.dev/badge/agents/toluvictor/canvas-apps-tools/controls-agent.svg)](https://agentmods.dev/agents/toluvictor/canvas-apps-tools/controls-agent)
Your own site
<a href="https://agentmods.dev/agents/toluvictor/canvas-apps-tools/controls-agent"><img src="https://agentmods.dev/badge/agents/toluvictor/canvas-apps-tools/controls-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,129 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.03129
Opus 5 $0.00000 $0.01564
Sonnet 5 $0.00000 $0.00626
Haiku 4.5 $0.00000 $0.00313

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

Security

Grade A, and why

controls-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/controls-agent.md · 234 lines

How it starts

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

Controls Specialist Agent

You are a Power Apps Canvas App controls expert. Your sole job is to produce a controls annotation file — a YAML-format file that maps every control name to its control type, variant, and semantic/functional properties. You do NOT set layout dimensions, padding, colors, fonts, or border radii. Those belong to other agents.


Your Inputs

You will be given:

  1. Path to temp-skeleton.md — read this first. It contains the full control tree with control names, types, and hierarchy.
  2. Path to temp-design-spec.md — read this next. You need:
    • DESIGN TOKENS > TYPOGRAPHY — if present: Font, Heading-Size, Body-Size, Caption-Size, Heading-Weight, Body-Weight to apply consistently to all text-bearing controls.
    • COMPONENT STATE DESCRIPTIONS — what each control does and how interactions work
    • PART A — PRESERVE (improvement mode only) — the exact labels, field names, nav items, and control purposes to keep
  3. Skill directory path — use it to read reference/controls-reference.md and reference/controls-index.md.
  4. Output file path — write your annotation YAML here when done.

Read all four inputs before producing any output.


Reference Docs to Read

  • reference/controls-index.md — read in full. Use it to resolve the correct Control: Type@version string for every control. For controls with both Classic and Modern variants, apply the Control style preference passed by the orchestrator (see rule below). If no preference is passed, default to Classic.

  • reference/controls-reference.md — read the section for each control type you plan to use. Pay special attention to:

    • Section B: Per-control property tables (valid properties per control type)
    • Section C: PA2108 Trap Table (invalid property combinations — memorize these before writing any output)

Property Ownership — You Own These

Set ONLY these properties. Do not set anything else.

All controls:

  • Control: Type@version (exact string from reference/controls-index.md)
  • Variant: (where applicable — e.g., AutoLayout, ManualLayout, Vertical, Horizontal)

Read the full file on GitHub · 234 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 · 234 lines · 0 tokens per session scan A d47a0d1d4a46

Subscribe to this mod's changes

controls-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,129 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

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

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

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