allium
v3.16.0Velocity through clarity. Includes 7 skills.
By JUXTLicense: MIT511 GitHub starsUpdated 3 weeks ago
Directory evidence
- Runtimes
- Codex and Claude Code
- Parsed components
- 7 skill or MCP entries
- Source updated
- Sep 27, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install allium for Codex and Claude Code
codex plugin marketplace add IchenDEV/agent-plugin-mkt
codex plugin marketplace upgrade agent-plugin-marketplace
codex plugin add allium@agent-plugin-marketplacePaste and run these commands in a terminal with Codex. They add and refresh the PluginsMP catalog, then install this plugin.
Compatibility: the page URL and API slug “allium-2” remain stable.
- Codex:
allium-2@agent-plugin-marketplace→allium@agent-plugin-marketplace
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/juxt/alliumClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The repository root is the plugin root.
Plugin files
├── .codex-plugin/plugin.json├── .claude-plugin/plugin.json├── skills/allium/SKILL.md├── skills/distill/SKILL.md├── skills/elicit/SKILL.md├── skills/propagate/SKILL.md├── skills/tend/SKILL.md├── skills/weed/SKILL.md└── skills/witness/SKILL.md
Included Skills7
Give your AI agents something more useful than a prompt. Velocity through clarity.
Extract an Allium specification from an existing codebase. Use when the user has existing code and wants to distil behaviour into a spec, reverse engineer a specification from implementation, generate a spec from code, turn implementation into a behavioural specification, or document what a codebase does in Allium terms.
Run a structured discovery session to build an Allium specification through conversation. Use when the user wants to create a new spec from scratch, elicit or gather requirements, capture domain behaviour, specify a feature or system, define what a system should do, or is describing functionality and needs help shaping it into a specification.
Generate tests from Allium specifications. Use when the user wants to propagate tests, generate test files from a spec, write tests for a specification, create property-based tests, produce state machine tests, check test coverage against spec obligations, or understand what tests a specification requires.
Tend the Allium garden. Use when the user wants to write, edit, update, add to, improve, clarify, refine, restructure, fix or migrate Allium specs. Covers adding entities, rules, triggers, surfaces and contracts, fixing syntax or validation errors, renaming or refactoring within specs, migrating specs to a new language version, and translating requirements into well-formed specifications. Pushes back on vague requirements.
Weed the Allium garden. Find where Allium specifications and implementation code have diverged, and help resolve the divergences. Use when the user wants to check spec-code alignment, compare specs against implementation, audit for spec drift or violations, sync specs with code or code with specs, or verify whether the implementation matches what the spec says.
Independently witness that an Allium loop's convergence claim is true and was reached honestly. Use when the user wants to verify a loop's self-report, confirm tests really pass and no generated test was weakened, produce a convergence certificate or witness record, gate CI on a trustworthy signal, or check that an autonomous run did not cheat its way to green.
Plugin manifests2
{
"name": "allium",
"version": "3.16.0",
"description": "Velocity through clarity.",
"author": {
"name": "JUXT",
"url": "https://juxt.pro"
},
"homepage": "https://allium-lang.org/",
"repository": "https://github.com/juxt/allium",
"license": "MIT",
"keywords": [
"specification",
"behaviour",
"behavior",
"domain-modelling",
"BDD",
"property-based-testing",
"generative-tests"
],
"skills": "./skills/",
"interface": {
"displayName": "Allium",
"shortDescription": "Behavioural specifications for agentic engineering",
"longDescription": "Write, maintain, review and propagate Allium behavioural specifications alongside implementation work.",
"developerName": "JUXT",
"category": "Coding",
"capabilities": [
"Read",
"Write",
"Interactive"
],
"websiteURL": "https://allium-lang.org/",
"defaultPrompt": [
"Draft an Allium spec for this feature.",
"Review this .allium spec for gaps.",
"Generate test obligations from this spec."
],
"screenshots": []
}
}{
"name": "allium",
"version": "3.16.0",
"description": "Velocity through clarity.",
"author": {
"name": "JUXT",
"url": "https://juxt.pro"
},
"homepage": "https://allium-lang.org/",
"repository": "https://github.com/juxt/allium",
"license": "MIT",
"keywords": [
"specification",
"behaviour",
"behavior",
"domain-modelling",
"BDD",
"property-based-testing",
"generative-tests"
],
"skills": [
"./skills/allium",
"./skills/distill",
"./skills/elicit",
"./skills/propagate",
"./skills/tend",
"./skills/weed",
"./skills/witness"
],
"agents": [
"./agents/distill.md",
"./agents/propagate.md",
"./agents/tend.md",
"./agents/weed.md",
"./agents/witness.md"
],
"lspServers": {
"allium": {
"command": "allium-lsp",
"args": [
"--stdio"
],
"extensionToLanguage": {
".allium": "allium"
}
}
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[allium on Agent Plugins Marketplace](https://pluginsmp.com/plugins/allium-2)