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/joshsmithxrm/power-platform-developer-suite/gemini-triagegit clone --depth 1 https://github.com/joshsmithxrm/power-platform-developer-suiteWrote 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/joshsmithxrm/power-platform-developer-suite/gemini-triage)<a href="https://agentmods.dev/agents/joshsmithxrm/power-platform-developer-suite/gemini-triage"><img src="https://agentmods.dev/badge/agents/joshsmithxrm/power-platform-developer-suite/gemini-triage.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.1 | $0.00005 | $0.00319 |
| Opus 5 | $0.00003 | $0.00160 |
| Sonnet 5 | $0.00001 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
gemini-triage 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.
What it actually says
Gemini Triage Agent
Triage Gemini review comments on a pull request. For each comment:
- Read the referenced file at the specified line
- Check against the spec and constitution for design rationale
- Evaluate: is this a valid finding that warrants a code change?
- If valid: fix the code and commit with
git commit -m "fix(review): <description>" - If invalid: compose a brief dismissal rationale explaining why the suggestion doesn't apply
Output Format
After processing all comments, push any fixes (git push) and output this JSON array:
[
{
"id": <comment_id>,
"action": "fixed" | "dismissed",
"description": "Brief explanation of what was done",
"commit": "<sha>" | null
}
]
Rules
- Read the full file context, not just the diff line
- Check the constitution (specs/CONSTITUTION.md) before dismissing
- Fix real issues; dismiss style preferences and false positives
- Each fix gets its own commit — don't batch
- Push all fixes before outputting the JSON summary
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 · 49 lines · 5 tokens per session scan A 455900907d4f
gemini-triage is an agent published in the GitHub repository joshsmithxrm/power-platform-developer-suite (7 stars, last pushed 5d ago), licensed MIT. It adds 5 tokens to every session and 319 once invoked, about $0.0000 per session on Opus 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-08-31.
Other agents, from other repositories
write-tests-agent
Agent that determines what type of tests to write and invokes the appropriate skill. Currently supports UI tests via write-ui-tests skill and XAML tests via write-xaml-tests skill.
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.
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…
canvas-screen-builder
Implements or modifies one Canvas App screen from a shared plan and a screen-specific brief. Writes exactly one .pa.yaml file and performs self-QA without compiling. Called by the orchestrator in parallel with other builders, not directly by users.
genpage-edit-planner
Plans edits to an existing generative page. Reads the downloaded page artifacts (source, original prompt, config), analyzes the current implementation against the user's edit intent, presents an edit plan via plan mode, and writes genpage-edit-plan.md for the orchestrator to execute. Called by the genpage skill — not…
looping
Re-invoke agents safely with bounded loops, completion evaluators, AI judges, progress feedback, and approval escape behavior.