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-edit-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-edit-page)<a href="https://agentmods.dev/skills/cratis/ai/cratis-engineering-docs-edit-page"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-engineering-docs-edit-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.00061 | $0.00610 |
| Opus 5 | $0.00030 | $0.00305 |
| Sonnet 5 | $0.00012 | $0.00122 |
| Haiku 4.5 | $0.00006 | $0.00061 |
Grade A, and why
cratis-engineering-docs-edit-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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Edit a Cratis documentation page
Change an existing page in the repository that owns its source. This skill owns source discovery and integration of an edit. It does not create a new page, invent product facts, or perform visual QA.
Required inputs
Establish:
- the published URL or a distinctive passage;
- the intended correction;
- the owning product/client or site-level subject;
- authoritative product source for every changed technical claim;
- the owning repository's documentation gates.
Route near misses
- The requested page does not exist: defer to
cratis-engineering-docs-add-page. - The content needs a new document-type design or substantial fresh draft:
defer that content to
cratis-engineering-docs-authoring. - The request is to inspect rendered appearance or layout shift: defer to
cratis-engineering-docs-visual-qa. - The subject is not Cratis documentation: do not apply this skill.
- The correction depends on unverified product/API behavior: block the claim and identify the owning first-party source.
Source discovery
- Map product URLs to the owning product or client repository.
- Map cross-product/site-level URLs to the hand-authored Documentation site.
- Search owning sources by slug, title, or distinctive passage when mapping is uncertain.
- Reject generated/synchronized product pages as edit targets.
- Confirm the exact source path and proposed change before modifying bytes.
Read source-discovery.md for the boundary.
Editing workflow
- Read the page and preserve its document type and established voice.
- Verify every changed API, command, version, link destination, or support claim against first-party source.
- Ask for confirmation of the exact modified paths.
- Make the smallest coherent correction in the owning source.
- Update navigation only when the title or slug change requires it.
- Synchronize product content into the site; never edit synchronized output.
- Run the owning snippet/build/lint/link gates and the site build when the page is public.
- Report source checked, changed paths, verification, 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 · 71 lines · 61 tokens per session scan A efb527496bc8
cratis-engineering-docs-edit-page is a skill published in the GitHub repository Cratis/AI (2 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 610 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.