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 Cratis/AI --skill add-business-rulegit clone --depth 1 https://github.com/Cratis/AIWrote 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/cratis/ai/add-business-rule)<a href="https://agentmods.dev/skills/cratis/ai/add-business-rule"><img src="https://agentmods.dev/badge/skills/cratis/ai/add-business-rule/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/cratis/ai/add-business-rule"><img src="https://agentmods.dev/badge/skills/cratis/ai/add-business-rule.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.00032 | $0.01491 |
| Opus 5 | $0.00016 | $0.00745 |
| Sonnet 5 | $0.00006 | $0.00298 |
| Haiku 4.5 | $0.00003 | $0.00149 |
Grade A, and why
add-business-rule 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- add-business-rule — 100% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a business rule or event-store constraint to an existing command.
Choose the right mechanism
Pick by what the decision is — see vertical-slices.md "The decision matrix":
| Scenario | Use |
|---|---|
| Reusable value invariant (length, format, range) | ConceptValidator<T> on the concept type |
| Command-input / cross-field / pre-handler rule (incl. injected read-model/service checks) | CommandValidator<TCommand> with RuleFor(...) |
| Handler needs fetched/computed data before it can build the event | Provide() — fetch the data; short-circuit with ValidationResult.Error(...) if unusable |
| State-dependent rule that must hold under concurrency | inject the read model into Handle(), return Result<TEvent, ValidationResult> |
| Single-event uniqueness (most cases) | [Unique] attribute on the event type |
Multi-event uniqueness or needs RemovedWith |
IConstraint |
| Genuinely exceptional failure (bug, missing infra) | throw a custom domain exception |
Never throw for normal business rejection. A thrown exception from
Provide()/Handle()surfaces asHasExceptions/ HTTP 500 — not a validation result. Recoverable, user-facing rejections are validation: return them via a validator,Provide(), orResult<TEvent, ValidationResult>.
Business rules via DCB (read model as Handle() argument)
Use when the rule depends on Chronicle event-sourced state (current count, accumulated value) and must hold under concurrency. The framework injects the current read-model snapshot, resolved by the command's event-source id, before Handle() runs. Return a Result<TEvent, ValidationResult> — success carries the event, failure carries a typed validation error.
The read model must already exist in the slice ([ReadModel] + a model-bound projection). If it doesn't, add it first — see the add-projection / cratis-readmodel skills.
[Command]
public record AddItemToCart(CartId CartId, ItemId ItemId)
{
/// <summary>Adds the item; rejects when the cart already holds the maximum.</summary>
/// <param name="cart">The current cart summary (injected by event-source id).</param>
/// <returns>The event on success, or a validation error.</returns>
public Result<ItemAddedToCart, ValidationResult> Handle(CartSummary cart) =>
cart.ItemCount >= 3
? ValidationResult.Error("A cart can hold at most 3 items.")
: new ItemAddedToCart(ItemId);
}
What ships with it
1 file 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.
- 5d ago Changed b0d550f84e7e
- 9d ago First seen · 112 lines · 32 tokens per session scan A e94076cb3fc2
add-business-rule is a skill published in the GitHub repository Cratis/AI (2 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 1,491 once invoked, about $0.0002 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 skills, from other repositories
architecture-paradigm-cqrs-es
Applies CQRS and Event Sourcing for read/write separation and audit trails. Use when designing systems with complex domain logic or full state-change history.
event-driven-architecture
Event-driven architecture patterns with event sourcing, CQRS, and message-driven communication. Use when designing distributed systems, microservices communication, or systems requiring eventual consistency and scalability.
cqrs-event-sourcing
CQRS and Event Sourcing patterns for scalable, auditable systems with separated read/write models. Use when building audit-required systems, implementing temporal queries, or designing high-scale applications with complex domain logic.
Event Sourcing Testing
Testing event sourcing patterns including event store validation, projection testing, saga orchestration, and event versioning compatibility.
event-driven-architecture
Event-Driven Architecture Review: Reviews and designs event-driven systems — Event Sourcing, CQRS, Saga patterns, Domain Events, message brokers, and eventual consistency. Use when the user mentions events, event sourcing, CQRS, saga, choreography vs orchestration, Kafka architecture, event store, projections, read…
enterprise-architecture-patterns
Complete guide for enterprise architecture patterns including domain-driven design, event sourcing, CQRS, saga patterns, API gateway, service mesh, and scalability.