jezweb/claude-skills is a collection of skills, commands, plugins, settings, instructions, and hooks that guide the Claude Code CLI through development tasks and produce outputs such as project scaffolds, assets, documents, or deployed services. It is for developers using Claude Code with technologies and services including Cloudflare, React, Tailwind, Shopify, and WordPress. The catalogue entries are the project's own Claude Code workflow components.
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 jezweb/claude-skills --skill aussie-business-englishgit clone --depth 1 https://github.com/jezweb/claude-skillsWrote 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/jezweb/claude-skills/aussie-business-english)<a href="https://agentmods.dev/skills/jezweb/claude-skills/aussie-business-english"><img src="https://agentmods.dev/badge/skills/jezweb/claude-skills/aussie-business-english/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/jezweb/claude-skills/aussie-business-english"><img src="https://agentmods.dev/badge/skills/jezweb/claude-skills/aussie-business-english.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00078 | $0.00649 |
| Opus 5.5 | $0.00031 | $0.00260 |
| Sonnet 5.5 | $0.00016 | $0.00130 |
| Haiku 4.5 | $0.00008 | $0.00065 |
Grade A, and why
aussie-business-english 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 1mo 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Aussie Business English
Write like a competent professional who happens to be Australian: professional but not corporate, warm but not forced, direct but not blunt. Say it once, plainly, and stop.
Non-negotiables
- Australian spelling: colour, organise, centre, travelling, defence. Noun/verb pairs: licence/license, practice/practise.
- No filler words. Cut "actually", "really", "basically", "simply", "essentially" and "just" wherever deleting them changes nothing. Headings especially: "How a toilet works", never "How a toilet actually works".
- No AI tells. Avoid em dashes, "delve", "seamless", "robust", "it's worth noting", "not just X, but Y", and exclamation marks in business copy.
- Lead with the point. First sentence carries the answer or the ask. Short paragraphs, active voice, natural contractions. Be specific: "by Thursday", not "soon".
Tone
Default is friendly professional. Open with "Hi [Name]". Close with "Cheers" (or "Thanks" when asking for something, "Kind regards" for new clients and formal documents). Keep "Dear [Name]" and "Yours sincerely" for formal or legal letters only. Never "Dear Sir/Madam", "Best", or "Warm regards".
Match the reader: short message in, short reply out. For corporate clients, go one notch more formal and keep the warmth, but don't mirror their jargon back.
Bad news: direct and kind, one "sorry" at most, then the path forward. Saying no: brief reason, offer an alternative if you have one. Prices: state them plainly ("The cost is $4,500"), no hedging.
Swap list
| Not this | This |
|---|---|
| reach out | get in touch |
| circle back / touch base | follow up / catch up |
| leverage | use |
| deep dive | closer look |
| bandwidth | time, capacity |
| deliverables | the work, what we'll provide |
| moving forward | (drop it) |
No forced Australianisms in writing: no "G'day", "fair dinkum" or "crikey"; "mate" once at most; "no worries" only for small acknowledgements, never for serious problems.
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.
- 1mo ago First seen · 49 lines · 78 tokens per session scan A 207f565e7654
aussie-business-english is a skill published in the GitHub repository jezweb/claude-skills (1,084 stars, last pushed 18d ago), licensed MIT. It adds 78 tokens to every session and 649 once invoked, about $0.0003 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-03.
Other skills, from other repositories
react-i18n
Use when implementing translations in a React app (not Next.js) with react-i18next — useTranslation, namespaces, pluralization, Suspense.
lingui-best-practices
Implement internationalization with Lingui in React and JavaScript applications. Use when adding i18n, translating UI, working with Trans/useLingui/Plural, extracting messages, compiling catalogs, or when the user mentions Lingui, internationalization, i18n, translations, locales, message extraction, ICU…
migrate-i18next-to-lingui
Migrate i18next/react-i18next projects to Lingui. Use when the user wants to replace i18next, react-i18next, useTranslation, i18n.t(), Trans i18nKey, or i18next JSON catalogs with Lingui equivalents. Covers package installation, config setup, code transformation patterns, plural migration, namespace handling, and…
lingui-framework-setup
Set up Lingui in a React framework. Use when adding Lingui to a Next.js App Router, Vite, React Router 7, Remix, or TanStack Start project, when wiring locale detection, locale-prefixed URLs, or SSR locale resolution, or when a working setup breaks after a framework or build-tool upgrade.
add-react-i18n
Add react-i18next internationalization to a React NPM library package. Creates isolated i18n instance, translation files, modifies provider and components. Use when the user wants to add multi-language support to a React component library.
localization-toolkit
This skill should be used when setting up, auditing, or enforcing internationalization/localization in UI codebases (React/TS, i18next or similar, JSON locales), including installing/configuring the i18n framework, replacing hard-coded strings, ensuring en-US/zh-CN coverage, mapping error codes to localized messages…