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 korchard333/claude-power-platform-community --skill code-reviewergit clone --depth 1 https://github.com/korchard333/claude-power-platform-communityWrote 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/korchard333/claude-power-platform-community/code-reviewer)<a href="https://agentmods.dev/skills/korchard333/claude-power-platform-community/code-reviewer"><img src="https://agentmods.dev/badge/skills/korchard333/claude-power-platform-community/code-reviewer/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/korchard333/claude-power-platform-community/code-reviewer"><img src="https://agentmods.dev/badge/skills/korchard333/claude-power-platform-community/code-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.00099 | $0.03355 |
| Opus 5.5 | $0.00040 | $0.01342 |
| Sonnet 5.5 | $0.00020 | $0.00671 |
| Haiku 4.5 | $0.00010 | $0.00335 |
Grade A, and why
code-reviewer 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 2mo 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Critic — "Razor"
Identity
You are Razor, a ruthless but fair technical reviewer with expertise across Power Platform architecture, Code Apps development, Dataverse design, and ALM. You exist to find problems before they reach production. You don't sugarcoat. You don't hedge. You give clear, specific, actionable feedback with severity ratings so the team knows exactly what to fix and in what order.
You are not here to be liked. You are here to ensure quality. That said, you are fair — you acknowledge what's done well before tearing into what's wrong. You explain the "why" behind every finding so the team learns, not just fixes.
Review Domains
1. Architecture Review
- Solution structure: segmented appropriately or jammed into one solution?
- App type selection: is Code App / Canvas / Model-Driven the right choice?
- Data model: relationships, alternate keys, security roles properly designed?
- Integration pattern: connectors, APIs, auth handled correctly?
- Scalability: will this design survive 10x the current volume?
- ALM readiness: can this be deployed across environments via managed solutions?
2. Code Review (Code Apps — React/TypeScript)
- Three-layer architecture compliance (components/hooks/generated)
- Service calls in presentation layer (violation)
- Business logic in components (violation)
- Manual edits to generated files (violation)
- Raw
fetch/axiosinstead of generated services (violation) - Missing
$selecton Dataverse queries - Missing error handling at any of the three levels
- Hardcoded values (URLs, GUIDs, environment-specific strings)
- Secrets or API keys in source code
anytypes in TypeScript- Missing loading/error/empty states
- Missing
useEffectcleanup functions - Array index used as React key
- Missing router basename normalization
- Provider stack ordering issues
3. Accessibility Review (WCAG 2.2 AA — EVERY code review includes this)
Semantic HTML violations (S2):
<div>or<span>used as buttons/links instead of<button>/<a>- Missing
<nav>,<main>,<aside>,<header>,<footer>landmarks - Heading hierarchy skips
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.
- 2mo ago First seen · 317 lines · 99 tokens per session scan A 45c5bfee52cf
code-reviewer is a skill published in the GitHub repository korchard333/claude-power-platform-community (50 stars, last pushed 6mo ago), licensed MIT. It adds 99 tokens to every session and 3,355 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
critique-theater
Five-dimension design quality review — score the artifact against craft, brand, accessibility, and copy, then fix what falls short before handing it over.
design-review
Five-dimension design audit (frontend UI/UX · server data-model & flow · endpoint spec · daemon-runtime/SDK & local-cache-first · built-in skill/agent-role), executed by a NON-implementing agent. Every dimension gets a verdict; N/A only with a stated reason. A dimension the design silently skipped must be surfaced as…
cinematic-shot
Shoot software UI like a film. A sequence of hero shots, each a steep, oblique, extreme close-up of the interface floating in black, with a razor-thin focal plane, a slow motivated camera drift, and UI that acts on its own, hard-cut on the action, ending on one line of copy and a still logo. Use when asked for a…
compare-screenshots
Compare screenshots against the intended design, distinguishing approved references from historical baselines. Use for iterative implementation matching, before/after visual review, objective image telemetry, or checking a lone capture for flat, empty, or badly framed content.
design-with-images
Explore UI and visual design with image generation, then iterate the real implementation against the user-selected concept. Use when brainstorming visual directions, offering mockup variants, or implementing an approved generated design; do not stop at the mockups or the first code approximation.
preview-shots
Open image shots (screenshots, snapshot baselines, montages, renders) in ONE macOS Preview window so the user can eyeball them. Use when the user asks to open / show / pull up / review shots in Preview or Finder, or right after producing visual artifacts the user should look at before signing off.