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 pcf-controlsgit 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/pcf-controls)<a href="https://agentmods.dev/skills/jnpiyush/agentx/pcf-controls"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/pcf-controls/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/pcf-controls"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/pcf-controls.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.00074 | $0.01138 |
| Opus 5.5 | $0.00030 | $0.00455 |
| Sonnet 5.5 | $0.00015 | $0.00228 |
| Haiku 4.5 | $0.00007 | $0.00114 |
Grade A, and why
pcf-controls 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PCF Code Components
Purpose: emit a TypeScript PCF control that builds with
pac pcf+ npm and packs into a solution -- the pro-code escape hatch when canvas/model-driven controls are not enough.
When to Use
- A required UX (custom chart, map, rich editor, signature pad) is not expressible with stock controls
- Reusing a JS/TS library inside a Power Apps form or canvas app
- Replacing a single field or a whole dataset (grid) with custom rendering
First decide low-code vs pro-code (see architecture/low-code-vs-pro-code). PCF is pro-code: it carries a build pipeline and maintenance cost.
Project Layout
<control-root>/
<ControlName>/
ControlManifest.Input.xml # manifest: type-group, properties, resources
index.ts # the control class (lifecycle)
generated/ # ManifestTypes.d.ts (pac generates)
package.json # pcf-scripts, pcf-start, build
pcfproj / .pcfproj # MSBuild project
tsconfig.json
Scaffold: pac pcf init --namespace Frontier --name IssueRating --template field (or --template dataset).
ControlManifest.Input.xml
<manifest>
<control namespace="Frontier" constructor="IssueRating" version="1.0.0"
display-name-key="Issue Rating" control-type="standard">
<property name="value" display-name-key="Value" of-type="Whole.None"
usage="bound" required="true" />
<resources>
<code path="index.ts" order="1" />
<css path="css/style.css" order="1" />
</resources>
</control>
</manifest>
usage="bound"ties the property to a column;usage="input"is a config value.of-typemust be a valid PCF type (SingleLine.Text,Whole.None,TwoOptions,OptionSet,DateAndTime.DateOnly, ...).control-type="standard"(field) vs adata-setelement for dataset/grid controls.
index.ts Lifecycle
import { IInputs, IOutputs } from "./generated/ManifestTypes";
export class IssueRating implements ComponentFramework.StandardControl<IInputs, IOutputs> {
private container: HTMLDivElement;
private notifyOutputChanged: () => void;
private value: number;
public init(
context: ComponentFramework.Context<IInputs>,
notifyOutputChanged: () => void,
state: ComponentFramework.Dictionary,
container: HTMLDivElement
): void {
this.container = container;
this.notifyOutputChanged = notifyOutputChanged;
}
public updateView(context: ComponentFramework.Context<IInputs>): void {
this.value = context.parameters.value.raw ?? 0;
// render into this.container from context.parameters (re-runs on every change)
}
public getOutputs(): IOutputs {
return { value: this.value }; // pushed back to the bound column
}
public destroy(): void {
// remove listeners / unmount
}
}
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 55ee3beff98a
- 1mo ago First seen · 122 lines · 74 tokens per session scan A 8beef3df7fec
pcf-controls is a skill published in the GitHub repository jnPiyush/AgentX (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 74 tokens to every session and 1,138 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.
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…