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 DevExpress/agent-skills --skill devexpress-reports-blazorgit clone --depth 1 https://github.com/DevExpress/agent-skillsWrote 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/devexpress/agent-skills/devexpress-reports-blazor)<a href="https://agentmods.dev/skills/devexpress/agent-skills/devexpress-reports-blazor"><img src="https://agentmods.dev/badge/skills/devexpress/agent-skills/devexpress-reports-blazor/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/devexpress/agent-skills/devexpress-reports-blazor"><img src="https://agentmods.dev/badge/skills/devexpress/agent-skills/devexpress-reports-blazor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 279 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.00155 | $0.08609 |
| Opus 5 | $0.00077 | $0.04304 |
| Sonnet 5 | $0.00031 | $0.01722 |
| Haiku 4.5 | $0.00015 | $0.00861 |
Grade A, and why
devexpress-reports-blazor 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 12d 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 — 462 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevExpress Blazor Reporting — Viewer & Designer Integration
Integrates DevExpress report viewing and designing into Blazor applications. Five components across three families cover every Blazor hosting model.
This skill covers Blazor UI component integration only. For creating reports programmatically (bands, controls, data binding, export), use the devexpress-reports-core skill.
Skill boundary — hard stop: This skill does NOT generate
XtraReportsubclasses, band declarations (DetailBand,GroupHeaderBand), or control code (XRLabel,XRTable, etc.). If a report class is needed, switch todevexpress-reports-corefor that part, get the class name or instance, then return here to wire it into the viewer.
Agent Workflow — Three Required Phases
Do not write any code until all three phases are complete. This ensures you load the correct reference files and generate a single coherent step-by-step plan.
- Phase 1 — Search the project and ask clarifying questions for any unknowns
- Phase 2 — Apply the decision gates to select the exact component and architecture
- Phase 3 — Load the matching reference files, merge their steps, present the plan, then execute
Phase 1 — Preflight: Gather Context
Step 1 — Automated Discovery (Do Before Asking Anything)
Run these searches in the project before asking the developer:
-
Installed packages:
dotnet list package→ look forDevExpress.Blazor.Reporting.*and their versions -
Blazor configuration classification — follow this 4-step algorithm and record the result before selecting any component:
Step A — Solution structure: Find all
.csprojfiles. Is there a.Clientproject (name suffix or a<ProjectReference>from a server project pointing to a client project)?Step B — Server
Program.cs(look forAddRazorComponentscall chain):What is found Preliminary result AddRazorComponents()with noAddInteractiveServerComponents()orAddInteractiveWebAssemblyComponents()→ Static AddInteractiveServerComponents()only→ Interactive Server AddInteractiveWebAssemblyComponents()only→ Interactive WebAssembly (Client + Server) Both AddInteractiveServerComponents()+AddInteractiveWebAssemblyComponents()→ Auto candidate; confirm in Step D
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/quickstart-native-viewer.cs 3.2 KB
- references/customizing-js-designer.md 14 KB
- references/customizing-js-viewer.md 19 KB
- references/customizing-native-viewer.md 16 KB
- references/getting-started-js-designer-interactive-wasm.md 19 KB
- references/getting-started-js-designer-server.md 15 KB
- references/getting-started-js-designer-standalone-wasm.md 14 KB
- references/getting-started-js-viewer-interactive-wasm.md 7.4 KB
- references/getting-started-js-viewer-server.md 6.0 KB
- references/getting-started-js-viewer-standalone-wasm.md 7.8 KB
- references/getting-started-native-viewer.md 13 KB
- references/resolving-report-names.md 30 KB
- references/troubleshooting.md 9.2 KB
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.
- 12d ago First seen · 462 lines · 155 tokens per session scan A 96b995fd5db0
devexpress-reports-blazor is a skill published in the GitHub repository DevExpress/agent-skills (53 stars, last pushed 25d ago), licensed MIT. It adds 155 tokens to every session and 8,609 once invoked, about $0.0008 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-30.
Other skills, from other repositories
avalonia-viewmodels-zafiro
Optimal ViewModel and Wizard creation patterns for Avalonia using Zafiro and ReactiveUI.
avalonia-zafiro-development
Mandatory skills, conventions, and behavioral rules for Avalonia UI development using the Zafiro toolkit.
convert-blazor-server-to-webapp
Guides conversion of a pre-.NET 8 Blazor Server app into a .NET 8+ Blazor Web App. USE FOR: migrating apps that use AddServerSideBlazor and MapBlazorHub to the AddRazorComponents/MapRazorComponents model, converting Host.cshtml to an App.razor root component, replacing blazor.server.js with blazor.web.js, migrating…
create-blazor-project
Create a new ASP.NET Core web application or web site using Blazor. USE FOR: creating a new Blazor web app, scaffolding a new web project, starting a new web site, choosing render modes (Static SSR, Interactive Server, Interactive WebAssembly, Auto), running dotnet new blazor with the right options, setting up initial…
use-js-interop
Add, review, or fix JavaScript interop in Blazor components. USE FOR: calling JavaScript from Blazor, calling .NET from JavaScript, collocated .razor.js modules, IJSRuntime, IJSObjectReference lifecycle, DotNetObjectReference, ElementReference, timing rules for when JS is available, IAsyncDisposable disposal of JS…
coordinate-components
Share state between components that don't have a direct parent-child parameter relationship, using cascading values, scoped services with change events, or CascadingValueSource via DI. USE WHEN the user needs a CascadingParameter or CascadingValue that works across render mode boundaries, a shopping cart or…