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 cratis-chronicle-compliancegit 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/cratis-chronicle-compliance)<a href="https://agentmods.dev/skills/cratis/ai/cratis-chronicle-compliance"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-chronicle-compliance/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/cratis-chronicle-compliance"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-chronicle-compliance.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.00097 | $0.02687 |
| Opus 5 | $0.00048 | $0.01344 |
| Sonnet 5 | $0.00019 | $0.00537 |
| Haiku 4.5 | $0.00010 | $0.00269 |
Grade A, and why
cratis-chronicle-compliance 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 2d 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chronicle compliance and personal data
Chronicle keeps events forever, so personal data cannot be deleted from the log. Chronicle protects it by encrypting each marked value under a key owned by the subject, and erases it by destroying that key. Decide the subject before you decide the event shape — the subject is what erasure operates on.
Verified product sources
This skill is verified against this exact public release:
| Package | Version | Purpose |
|---|---|---|
Cratis.Chronicle |
16.45.3 |
Cratis.Chronicle.Compliance.GDPR, Cratis.Chronicle.SubjectAttribute, IEventSequence.Redact, IReadModels.Release |
Cratis.Chronicle.CodeAnalysis |
16.45.3 |
CHR0026, CHR0034, CHR0035, CHR0043, CHR0046 |
Reverify product sources before claiming support for another version.
Mark personal data with [PII]
Cratis.Chronicle.Compliance.GDPR.PIIAttribute marks a value as personal data.
It targets a class, a property, or a constructor parameter, and it is not
repeatable.
using Cratis.Chronicle.Compliance;
using Cratis.Chronicle.Compliance.GDPR;
[EventType]
public record <PersonEventName>(
[property: PII] string <PersonalPropertyName>,
<NonPersonalType> <BusinessPropertyName>);
On a positional record the attribute must be written as [property: PII] or
placed on the constructor parameter; Chronicle looks for it on the property, the
property's declaring type, the property's own type, and the matching primary
constructor parameter.
Marking the concept type itself makes the value personal everywhere it appears, which is usually what you want for an email, a phone number, or a personal name:
[PII]
[ComplianceDetails("<why this value is collected and under what basis>")]
public record <ConceptName>(string Value) : ConceptAs<string>(Value);
PIIAttribute accepts an optional details string, but Chronicle never reads
it. The rationale that actually reaches the event schema comes from
Cratis.Chronicle.Compliance.ComplianceDetailsAttribute. Write [PII] for the
marker and [ComplianceDetails("...")] for the reason; do not write
[PII("reason")] and expect the reason to be recorded.
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.
- 2d ago First seen · 247 lines · 97 tokens per session scan A 9bf9b6c51fb8
cratis-chronicle-compliance is a skill published in the GitHub repository Cratis/AI (2 stars, last pushed today), licensed MIT. It adds 97 tokens to every session and 2,687 once invoked, about $0.0005 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-09-06.
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.
orchardcore-dnc-registry
Skill for configuring national and local do-not-call registry checks in CrestApps Orchard Core including Azure Blob Storage for uploaded local lists. Covers import suppression, provider settings, E.164 normalization, CSV processing, registry extensions, and tenant-aware Azure storage. Use this skill when requests…
orchardcore-audit-trail
Skill for configuring audit trail in Orchard Core. Covers audit event recording, AuditTrailPart for content tracking, event filtering and sorting, audit settings configuration, custom audit event providers, and audit trail feature setup. Use this skill when requests mention Orchard Core Audit Trail, Configure Audit…
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.
enterprise-architecture-patterns
Complete guide for enterprise architecture patterns including domain-driven design, event sourcing, CQRS, saga patterns, API gateway, service mesh, and scalability.
dotnet-analyzer-security-deps
Scan .NET projects for security vulnerabilities (OWASP Top 10), NuGet dependency health, CVE exploits, license compliance, and version conflicts using Roslyn and NuGet.org API. Use when the user asks to scan for security vulnerabilities, check for CVE, analyze dependency health, check license compliance, scan NuGet…