Borrowing it
Nothing to install: this file belongs to quarkusio/quarkus-workshop-langchain4j. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/quarkusio/quarkus-workshop-langchain4j/main/.agents/skills/workshop-docs-style/SKILL.mdgit clone --depth 1 https://github.com/quarkusio/quarkus-workshop-langchain4jWrote 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/quarkusio/quarkus-workshop-langchain4j/workshop-docs-style)<a href="https://agentmods.dev/skills/quarkusio/quarkus-workshop-langchain4j/workshop-docs-style"><img src="https://agentmods.dev/badge/skills/quarkusio/quarkus-workshop-langchain4j/workshop-docs-style/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/quarkusio/quarkus-workshop-langchain4j/workshop-docs-style"><img src="https://agentmods.dev/badge/skills/quarkusio/quarkus-workshop-langchain4j/workshop-docs-style.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.00053 | $0.06261 |
| Opus 5.5 | $0.00021 | $0.02504 |
| Sonnet 5.5 | $0.00011 | $0.01252 |
| Haiku 4.5 | $0.00005 | $0.00626 |
Grade A, and why
workshop-docs-style 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 21d 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workshop Documentation Style Guide
This guide captures the conventions established for the Quarkus LangChain4j workshop docs. It is self-contained for contributors to this repository; repeat a general writing rule here when workshop authors need it. The reference voice is Section 1, which was written by the project owner without AI assistance.
Voice and Tone
Write as a technical instructor talking to a developer sitting in front of their laptop. Be direct and practical. Avoid corporate enthusiasm ("Congratulations!", "Great!", "Easy right?") unless a brief one-liner fits naturally at the end of a section. Don't start pages with "In this step you will learn..." laundry lists.
Stay in the reader's exercise
Keep learner-facing prose about the business scenario, system behavior, and actions the reader can take. Do not insert workshop-author commentary about how chapters are being built, what is planned or omitted, or which features have not been implemented. For example, delete asides such as "The section will build toward checking offers with external services, but the current planner has no extras catalog or reservation service." Keep roadmap and implementation-status details in planning documents. An unfinished chapter can retain one short "Coming soon" notice without repeating that status throughout its prose.
Do not narrate our local testing history or conversations with the project owner. Dates, model-specific outcomes, run identifiers, incidental screenshot details, and accounts of what worked during author testing belong in maintenance notes, not the tutorial. Explain what the reader should inspect and why. Preserve setup instructions and limitations that affect the exercise, such as a simulated booking, state lost on restart, or a price covering vehicle rental only. Put these beside the relevant action instead of adding general disclaimers to the scenario.
Connected prose
Concise does not mean a succession of short, abrupt sentences. Develop each paragraph around a connected idea, using cause, contrast, or sequence to help one sentence lead into the next. Vary sentence length naturally, without turning every explanation into either clipped statements or one long sentence.
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.
- 21d ago Changed · +18 lines 1e12bce10c3b
- 25d ago Changed · +16 lines 3afc70fa4501
- 27d ago Changed · +12 lines 66c3bb20f52b
- 1mo ago Changed · +2 lines 579a0edc2e92
- 1mo ago Changed · +23 lines 531fc2e4701c
- 1mo ago Changed · +46 lines 763d83606046
- 1mo ago First seen · 172 lines · 53 tokens per session scan A 0860df326c53
workshop-docs-style is a skill published in the GitHub repository quarkusio/quarkus-workshop-langchain4j (112 stars, last pushed yesterday), licensed Apache-2.0. It adds 53 tokens to every session and 6,261 once invoked, about $0.0002 per session on Opus 5.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-15.
Other skills, from other repositories
ai-tutor
Use when user asks to explain, break down, or help understand technical concepts (AI, ML, or other technical topics). Makes complex ideas accessible through plain English and narrative structure. Use the provided scripts to transcribe videos.
hps-bauhaus
A visual-design fundamentals course for new brand designers — grid, type, color, and the exercises that build the eye. Built as a decision-grade professional training deck for junior designers, new hires.
html-ppt-zhangzara-daisy-days
A customer-success workshop onboarding users to a project-management app — the first-value path and the habits that retain. Built as a decision-grade professional training deck for new customers, CS team.
html-ppt-zhangzara-retro-windows
An IT security-awareness training on spotting phishing — the tells, the drill, and what to do in the first 60 seconds. Built as a decision-grade professional training deck for all employees.
canvas
Fetch Canvas LMS courses and assignments via API token.
playwright
Use when the task requires capturing or automating a real browser from the terminal.