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-xaf-filteringgit 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-xaf-filtering)<a href="https://agentmods.dev/skills/devexpress/agent-skills/devexpress-xaf-filtering"><img src="https://agentmods.dev/badge/skills/devexpress/agent-skills/devexpress-xaf-filtering/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-xaf-filtering"><img src="https://agentmods.dev/badge/skills/devexpress/agent-skills/devexpress-xaf-filtering.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.00167 | $0.02593 |
| Opus 5.5 | $0.00067 | $0.01037 |
| Sonnet 5.5 | $0.00033 | $0.00519 |
| Haiku 4.5 | $0.00017 | $0.00259 |
Grade A, and why
devexpress-xaf-filtering 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 10d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevExpress XAF — Filtering
This skill covers all data filtering techniques in XAF applications. EF Core is the recommended ORM; all examples default to EF Core patterns unless stated otherwise. XPO is also supported.
Composite skill: If the target project uses XPO, also load the
devexpress-xaf-filtering-xposkill forXPCollectioncriteria,XPQuery<T>, and XPO-specific operator classes.
Prerequisites & Installation
Filtering is part of the core XAF framework — no additional module registration is required.
NuGet Packages
| Package | Purpose |
|---|---|
DevExpress.Data |
CriteriaOperator, BinaryOperator, GroupOperator, FunctionOperator, and all criteria classes (DevExpress.Data.Filtering namespace) |
DevExpress.ExpressApp |
IObjectSpace filtering methods, CollectionSource.Criteria, FilterController, SetFilterAction, ListViewFilterAttribute |
DevExpress.ExpressApp.Filtering |
SearchClassOptionsAttribute, SearchMemberOptionsAttribute — Full Text Search configuration |
DevExpress.Persistent.Base |
DataSourcePropertyAttribute, DataSourceCriteriaAttribute — lookup filtering |
All packages are included in every XAF project by default.
Using Statements
using DevExpress.Data.Filtering; // CriteriaOperator, BinaryOperator, GroupOperator, etc.
using DevExpress.ExpressApp; // IObjectSpace, CollectionSource, ViewController
using DevExpress.Persistent.Base; // DataSourcePropertyAttribute, DataSourceCriteriaAttribute
Custom Function Registration
ICustomFunctionOperator implementations must be registered at application startup in MySolution.Module\Module.cs:
public override void Setup(XafApplication application) {
base.Setup(application);
CriteriaOperator.RegisterCustomFunction(new MyCustomFunction());
}
ORM Detection
Before generating filtering code, determine which ORM the project uses:
- Check for
DevExpress.ExpressApp.EFCoreorDevExpress.ExpressApp.XpoNuGet references. - Check business classes — EF Core uses auto-properties +
DbContext; XPO usesXPObject/BaseObjectwithSessionconstructor. - If XPO is detected, load the
devexpress-xaf-filtering-xposkill for XPO-specific filtering patterns.
What ships with it
5 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.
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.
- 10d ago First seen · 196 lines · 167 tokens per session scan A 66728ac02852
devexpress-xaf-filtering is a skill published in the GitHub repository DevExpress/agent-skills (66 stars, last pushed 11d ago), licensed MIT. It adds 167 tokens to every session and 2,593 once invoked, about $0.0007 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-10-20.
Other skills, from other repositories
TEMPLATE
../../../agents/personas/TEMPLATE.md.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…
flyway-migrations
Use when creating database migrations, schema changes, seed data, or any SQL that modifies database structure. Covers Flyway naming conventions, versioning, and safe migration patterns.
spring-data-redis
Use when implementing caching, session storage, rate limiting, or any Redis integration. Covers cache-aside pattern, key naming, TTL strategy, and serialization config.
transactional-patterns
Use when defining or debugging Spring Boot 3 database transaction boundaries, rollback, propagation, optimistic-lock retries, or commit-bound events. For duplicate HTTP commands use idempotency-patterns; for reactive transactions use webflux-reactive-patterns.
spring-data-jpa
Use when generating JPA entities, repositories, queries, or anything touching the persistence layer. Covers entity conventions, N+1 prevention, projections, and query patterns.