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-mcp-inspectiongit 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-mcp-inspection)<a href="https://agentmods.dev/skills/cratis/ai/cratis-chronicle-mcp-inspection"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-chronicle-mcp-inspection/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-mcp-inspection"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-chronicle-mcp-inspection.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.00086 | $0.00739 |
| Opus 5 | $0.00043 | $0.00369 |
| Sonnet 5 | $0.00017 | $0.00148 |
| Haiku 4.5 | $0.00009 | $0.00074 |
Grade A, and why
cratis-chronicle-mcp-inspection 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 8d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chronicle MCP inspection guidance
Treat access to a running Chronicle store as access to live operational data. Classify the request before discussing a tool, and do not infer safety from a name, description, or protocol hint.
Current authority boundary
This package has no admitted Chronicle MCP tool or prompt. The upstream source contract is unverified, so every tool and prompt remains evidence-blocked.
Read the generated classifications before answering:
- Observational guidance records subjects admitted for bounded read-only guidance. It is currently empty.
- Blocked guidance records the deny-all boundary.
Do not invoke, simulate, install, configure, or provide an invocation payload for a tool or prompt while the observational inventory is empty.
What this skill can do
- Classify the user's intent as observational, effectful, or unknown.
- Explain why unknown or incompletely evidenced behavior remains blocked.
- Help the user confirm the intended store, event store, namespace, and data sensitivity before any future observational access.
- Interpret output the user has already supplied after they have redacted secrets, personal data, business payloads, and identifying metadata.
- Recommend narrowing a request by identifier, type, sequence range, or page when that can reduce data exposure without inventing a tool signature.
Classification rules
Use these classes independently from package trust:
- Classification-only — reasoning about a request or already-redacted output; no external call.
- Observational — a bounded read proven by immutable implementation, schema, effect, output-classification, and redaction evidence.
- Effectful — creates, changes, deletes, executes, publishes, accesses credentials, or transmits unbounded or open-world data.
- Unknown — evidence is absent, stale, incomplete, or conflicting.
Only an observational subject with a passive-allowed disposition may ever be
selected. Effectful and unknown subjects remain blocked. A read-only annotation
or read-sounding name is corroboration at most; implementation evidence owns the
classification.
What ships with it
3 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.
- 8d ago First seen · 80 lines · 86 tokens per session scan A 2dd58bf9e42a
cratis-chronicle-mcp-inspection is a skill published in the GitHub repository Cratis/AI (2 stars, last pushed yesterday), licensed MIT. It adds 86 tokens to every session and 739 once invoked, about $0.0004 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-03.
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.
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.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.