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-web-workbenchgit 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-web-workbench)<a href="https://agentmods.dev/skills/cratis/ai/cratis-chronicle-web-workbench"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-chronicle-web-workbench.svg" alt="Measured on agentmods" 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.00098 | $0.01873 |
| Opus 5 | $0.00049 | $0.00937 |
| Sonnet 5 | $0.00020 | $0.00375 |
| Haiku 4.5 | $0.00010 | $0.00187 |
Grade A, and why
cratis-chronicle-web-workbench 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 yesterday.
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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Chronicle browser Workbench
The Workbench is a React application the Chronicle server serves alongside its gRPC and HTTP surfaces. It is the richest view of a running store — and the only place several irreversible operations exist. Treat it as full plaintext access to the event log.
"Workbench" names two different products. This skill is about the browser
Workbench served by the Chronicle server. The terminal Workbench is a separate
full-screen view inside the cratis CLI, with a smaller, read-mostly capability
set.
Verified product sources
This skill is verified against this exact source:
| Package | Version | Purpose |
|---|---|---|
Cratis.Chronicle |
16.45.2 |
the Workbench application, its hosting, screens, and commands |
Reverify before claiming a screen, route, command, or configuration key for another version.
Reach it
The Workbench is served by the Chronicle server on the kernel port, which
defaults to 35000. That port is TLS, because HTTP/1.1 and HTTP/2 are
multiplexed on it through ALPN — so the browser URL is https://<host>:35000/,
not http://. In a non-development build the server refuses to start without a
certificate.
Configuration lives under Cratis:Chronicle, bound from a chronicle.json at
the host root and from environment variables prefixed Cratis__Chronicle__.
| Key | Default | Effect |
|---|---|---|
Features:Workbench |
true |
serves the Workbench |
Features:Api |
true |
serves the HTTP API |
Authentication:Enabled |
true |
token authority, identity endpoints, bootstrap admin |
Features:Workbench is ANDed with Features:Api. Setting Features:Api to
false silently disables the Workbench, because the Workbench is nothing but a
client of that API.
An application that embeds Chronicle can host the Workbench as a side-car web server instead, on its own port and optionally under a base path.
The security facts that decide whether to expose it
Read these before putting a Workbench on any reachable network.
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.
- yesterday First seen · 178 lines · 98 tokens per session scan A 8878e1fb60ee
cratis-chronicle-web-workbench is a skill published in the GitHub repository Cratis/AI (2 stars, last pushed yesterday), licensed MIT. It adds 98 tokens to every session and 1,873 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.
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.
optimizing-ef-core-queries
Optimize and improve the performance of slow Entity Framework Core (EF Core) queries: make them generate less SQL, make fewer database round-trips, and return results faster. Use whenever an EF Core or DbContext query or data-access path is slow or should be made faster — whether or not EF Core owns the database…
cqrs-event-sourcing-architect
CQRS pattern, event stores, projections, eventual consistency. Activate on: CQRS, event sourcing, event store, read model, projection, aggregate, domain event, command handler. NOT for: message broker setup (use event-driven-architecture-expert), database optimization (use data-warehouse-optimizer).
triage-issues
Triage GitHub issues in the googleapis/mcp-toolbox repo: propose the correct labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a…
postgresql-indexing
PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing…