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 agentmods add skills/juxt/claude-plugins/alliumnpx skills add juxt/claude-plugins --skill alliumgit clone --depth 1 https://github.com/juxt/claude-pluginsWhat 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 | $0.00018 | $0.03775 |
| Opus 5 | $0.00009 | $0.01887 |
| Sonnet 5 | $0.00004 | $0.00755 |
| Haiku 4.5 | $0.00002 | $0.00378 |
Grade A, and why
allium 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 2d 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.
This is a copy
100% identical to allium — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 342 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Allium
Allium is a formal language for capturing software behaviour at the domain level. It sits between informal feature descriptions and implementation, providing a precise way to specify what software does without prescribing how it's built.
The name comes from the botanical family containing onions and shallots, continuing a tradition in behaviour specification tooling established by Cucumber and Gherkin.
Key principles:
- Describes observable behaviour, not implementation
- Captures domain logic that matters at the behavioural level
- Generates integration and end-to-end tests (not unit tests)
- Forces ambiguities into the open before implementation
- Implementation-agnostic: the same spec could be implemented in any language
Allium does NOT specify programming language or framework choices, database schemas or storage mechanisms, API designs or UI layouts, or internal algorithms (unless they are domain-level concerns).
Routing table
| Task | Tool | When |
|---|---|---|
Writing or reading .allium files |
this skill | You need language syntax and structure |
| Building a spec through conversation | elicit skill |
User describes a feature or behaviour they want to build |
| Extracting a spec from existing code | distill skill |
User has implementation code and wants a spec from it |
| Modifying an existing spec | tend skill |
User wants targeted changes to .allium files |
| Checking spec-to-code alignment | weed skill |
User wants to find or fix divergences between spec and implementation |
| Generating tests from a spec | propagate skill |
User wants to generate tests, PBT properties or state machine tests from a specification |
| Attesting a loop's convergence | witness skill |
User wants to independently confirm a run's convergence claim from ground truth — tests really pass, no generated test was weakened, no blocking question was silently parked |
| Driving the whole loop to convergence | this skill (see driving the loop) | User wants to build or reconcile a feature end to end — /allium <goal> runs the gather→act→verify→repeat loop autonomously until spec, tests and code agree |
What ships with it
17 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.
- references/actioning-findings.md 6.9 KB
- references/assessing-specs.md 5.5 KB
- references/driving-the-loop.md 21 KB
- references/integrating-slices.md 5.8 KB
- references/language-reference.md 105 KB
- references/migration-v1-to-v2.md 13 KB
- references/migration-v2-to-v3.md 14 KB
- references/patterns.md 92 KB
- references/recommended-loops.md 15 KB
- references/schemas/distill-result.schema.json 964 B
- references/schemas/ledger.schema.json 1.5 KB
- references/schemas/propagate-result.schema.json 2.3 KB
- references/schemas/tend-result.schema.json 975 B
- references/schemas/trace-entry.schema.json 2.3 KB
- references/schemas/weed-result.schema.json 2.0 KB
- references/schemas/witness-result.schema.json 2.0 KB
- references/test-generation.md 10.0 KB
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.
- 2d ago First seen · 342 lines · 18 tokens per session scan A bad4431c65c9
allium is a skill published in the GitHub repository juxt/claude-plugins (10 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 3,775 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to allium, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…