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-filtering-xpogit 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-xpo)<a href="https://agentmods.dev/skills/devexpress/agent-skills/devexpress-xaf-filtering-xpo"><img src="https://agentmods.dev/badge/skills/devexpress/agent-skills/devexpress-xaf-filtering-xpo/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-xpo"><img src="https://agentmods.dev/badge/skills/devexpress/agent-skills/devexpress-xaf-filtering-xpo.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.00130 | $0.02266 |
| Opus 5.5 | $0.00052 | $0.00906 |
| Sonnet 5.5 | $0.00026 | $0.00453 |
| Haiku 4.5 | $0.00013 | $0.00227 |
Grade A, and why
devexpress-xaf-filtering-xpo 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevExpress XAF — Filtering (XPO Sub-Skill)
This sub-skill extends devexpress-xaf-filtering with XPO-specific filtering patterns. The base skill covers CriteriaOperator syntax, IObjectSpace methods, and XAF filtering infrastructure — this skill covers the XPO layer underneath.
When to Use This Skill
Use this skill (in addition to the base skill) when:
- The XAF project uses XPO as its ORM
- You need to filter
XPCollection<T>withCriteriaOperator - You need
XPQuery<T>(LINQ to XPO) for type-safe queries - You need
XPViewfor lightweight read-only projections - You need to build criteria programmatically using
BinaryOperator,GroupOperator,FunctionOperator - You need server-mode data sources with filtering
- You need
Session.FindObjectorSession.GetObjects
Prerequisites & Installation
XPO filtering uses the same core criteria classes as the base filtering skill, plus XPO-specific collection and session APIs.
NuGet Packages
| Package | Purpose |
|---|---|
DevExpress.Xpo |
Session, UnitOfWork, XPCollection<T>, XPQuery<T>, XPView, XPInstantFeedbackSource, XPServerCollectionSource |
DevExpress.ExpressApp.Xpo |
XPObjectSpace — bridges IObjectSpace to XPO Session |
DevExpress.Data |
CriteriaOperator, BinaryOperator, GroupOperator, and all criteria classes (DevExpress.Data.Filtering namespace) |
These packages are included in XPO-based XAF projects created from the template.
Using Statements
using DevExpress.Data.Filtering; // CriteriaOperator, BinaryOperator, GroupOperator, etc.
using DevExpress.Xpo; // Session, XPCollection, XPQuery, XPView, SortProperty
using DevExpress.ExpressApp.Xpo; // XPObjectSpace — access Session from IObjectSpace
CriteriaOperator Class Hierarchy
All criteria operators live in DevExpress.Data.Filtering:
CriteriaOperator (abstract)
├── BinaryOperator — a op b (==, !=, <, >, <=, >=)
├── GroupOperator — AND / OR of multiple operands
├── UnaryOperator — NOT, IsNull
├── FunctionOperator — built-in & custom functions
├── ContainsOperator — collection element check
├── InOperator — value IN (list)
├── BetweenOperator — value BETWEEN (low, high)
├── AggregateOperand — aggregate over collection
├── JoinOperand — join non-associated objects
├── OperandProperty — property reference
├── OperandValue — literal value
└── ConstantValue — compile-time constant
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 · 174 lines · 130 tokens per session scan A 99405dc202b8
devexpress-xaf-filtering-xpo is a skill published in the GitHub repository DevExpress/agent-skills (66 stars, last pushed 11d ago), licensed MIT. It adds 130 tokens to every session and 2,266 once invoked, about $0.0005 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.