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-cli-terminal-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-cli-terminal-workbench)<a href="https://agentmods.dev/skills/cratis/ai/cratis-cli-terminal-workbench"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-cli-terminal-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.00099 | $0.01662 |
| Opus 5 | $0.00049 | $0.00831 |
| Sonnet 5 | $0.00020 | $0.00332 |
| Haiku 4.5 | $0.00010 | $0.00166 |
Grade A, and why
cratis-cli-terminal-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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The terminal Workbench
cratis chronicle workbench opens a full-screen terminal view over one event
store and namespace. It is the CLI's exploration surface: the same read-only
data the individual cratis chronicle … commands return, arranged so you can
move between observers, failures, jobs, events, projections and read models
without re-typing a connection.
"Workbench" names two different products. This skill is about the terminal
Workbench that ships in the cratis CLI. The browser Workbench is a separate
React application served by the Chronicle server, with a different and larger
capability set — including redaction and revision, which the terminal Workbench
does not have.
Verified product sources
This skill is verified against this exact source:
| Package | Version | Purpose |
|---|---|---|
Cratis.Cli |
2.4.0 |
cratis chronicle workbench, its views, keys, and actions |
Reverify before claiming a view, key binding, or action for another version.
cratis chronicle workbench --help and cratis llm-context are the authority
for the installed version.
Launch it
cratis chronicle workbench # active context, default event store and namespace
cratis chronicle workbench -e <store> -n <ns> # explicit event store and namespace
cratis chronicle workbench --interval <secs> # refresh cadence, default 5
It requires an interactive terminal and the table output format. Asking for
json, plain, or json-compact is rejected with a validation error — that is
the correct behavior, not a bug. When you need machine-readable output, use
the individual cratis chronicle … commands instead, which is also the right
choice inside a script, a pipeline, or an agent harness.
Connection, event store and namespace resolve exactly as they do for every other
cratis chronicle command: --server, then CHRONICLE_CONNECTION_STRING, then
the active context, then chronicle://localhost:35000. Confirm the context
before opening a view onto a production store.
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 · 157 lines · 99 tokens per session scan A 859ba1229380
cratis-cli-terminal-workbench is a skill published in the GitHub repository Cratis/AI (2 stars, last pushed yesterday), licensed MIT. It adds 99 tokens to every session and 1,662 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…