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-engineering-docs-add-pagegit 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-engineering-docs-add-page)<a href="https://agentmods.dev/skills/cratis/ai/cratis-engineering-docs-add-page"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-engineering-docs-add-page.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.00058 | $0.00663 |
| Opus 5 | $0.00029 | $0.00331 |
| Sonnet 5 | $0.00012 | $0.00133 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
cratis-engineering-docs-add-page 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 3d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a Cratis documentation page
Place one new page in the repository that owns its subject and wire it into the published Cratis documentation navigation. This skill owns placement and integration. It does not invent product content, edit an existing page, or perform visual QA.
Required inputs
Establish before changing files:
- Cratis product or cross-product subject;
- owning repository;
- approved destination and document type;
- page title and navigation label;
- authoritative product source for factual content;
- whether the page is product-owned or site-level.
If ownership or destination cannot be established from repository evidence, stop and return the unresolved decision instead of guessing.
Route near misses
- The page already exists: defer to
cratis-engineering-docs-edit-page. - Placement is approved but content is not drafted: defer content to
cratis-engineering-docs-authoring. - The request is to render or screenshot a page: defer to
cratis-engineering-docs-visual-qa. - The subject is not Cratis documentation: do not apply this skill.
- Product/API authority is missing: block factual drafting and identify the owning source needed.
Placement workflow
- Confirm the page does not already exist in the owning source repository.
- Choose the source root:
- product/client/contributor page: that repository's
Documentation/tree; - cross-product or site-level page: the
Cratis/Documentationsite's hand-authored content tree.
- product/client/contributor page: that repository's
- Confirm the document type and approved filename before creating it.
- Ask for confirmation of the exact new and modified paths.
- Create the source page using the approved content or invoke
cratis-engineering-docs-authoringfor the draft. - Wire the owning navigation source. For product docs, update the product ToC and the site synchronization bucket only when the current Documentation source proves both are required. For site-level pages, update the site's hand-authored navigation.
- Run source sync and verify that no navigation entries were dropped.
- Run the owning repository's build, snippet, lint, and link gates.
- Report the created page, navigation changes, authority checked, and visual QA still required.
What ships with it
2 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.
- 3d ago First seen · 74 lines · 58 tokens per session scan A 5dff5ee0dcc3
cratis-engineering-docs-add-page is a skill published in the GitHub repository Cratis/AI (2 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 663 once invoked, about $0.0003 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.
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.