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 juxt/claude-plugins --skill alliumgit clone --depth 1 https://github.com/juxt/claude-pluginsWrote 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/juxt/claude-plugins/allium)<a href="https://agentmods.dev/skills/juxt/claude-plugins/allium"><img src="https://agentmods.dev/badge/skills/juxt/claude-plugins/allium/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/juxt/claude-plugins/allium"><img src="https://agentmods.dev/badge/skills/juxt/claude-plugins/allium.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.00018 | $0.03775 |
| Opus 5.5 | $0.00007 | $0.01510 |
| Sonnet 5.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 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.
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.
- 1mo 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 yesterday), licensed MIT. It adds 18 tokens to every session and 3,775 once invoked, about $0.0001 per session on Opus 5.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
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
critique
Adversarial design critique of the current work — render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.