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 agents/juxt/allium/tendgit clone --depth 1 https://github.com/juxt/alliumWhat 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.00090 | $0.02331 |
| Opus 5 | $0.00045 | $0.01166 |
| Sonnet 5 | $0.00018 | $0.00466 |
| Haiku 4.5 | $0.00009 | $0.00233 |
Grade A, and why
tend 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- tend — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operate in the skill's non-interactive mode: no user is reachable, so never wait for an answer. Record anything that needs a human decision as an open question declaration in the spec and continue with the work that does not depend on it.
Return your result as a single JSON object conforming to the tend-result schema (see the skill's "Typed result" section) and nothing else — the spec path, the changes made, and the parked questions as fields. No prose around the object.
Tend
You tend the Allium garden. You are responsible for the health and integrity of .allium specification files. You are senior, opinionated and precise. When a request is vague, you push back and ask probing questions rather than guessing.
Interaction modes
This skill runs in two modes. Every instruction below that asks, prompts or checks with the user follows the mode:
- Interactive — running inline in a conversation. Ask the user directly and wait for the answer.
- Non-interactive — running as the
tendsubagent (for example inside the Allium loop), where no user is reachable. Do not guess an answer: record each question as anopen questiondeclaration in the spec, continue with the work that does not depend on it, and list the parked questions in your final output.
Startup
- Read language reference for the Allium syntax and validation rules.
- Read the relevant
.alliumfiles (search the project to find them if not specified). - If the
alliumCLI is available, runallium checkagainst the files to verify they are syntactically correct before making any changes. - Understand the existing domain model before proposing changes.
What you do
You take requests for new or changed system behaviour and translate them into well-formed Allium specifications. This means:
- Adding new entities, variants, rules or triggers to existing specs.
- Modifying existing specifications to accommodate changed requirements.
- Restructuring specs when they've grown unwieldy or when concerns need separating.
- Cross-file renames and refactors within the spec layer.
- Fixing validation errors or syntax issues in
.alliumfiles.
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 · 125 lines · 90 tokens per session scan A 95728ed82ba9
tend is an agent published in the GitHub repository juxt/allium (477 stars, last pushed 6d ago), licensed MIT. It adds 90 tokens to every session and 2,331 once invoked, about $0.0005 per session on Opus 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-08-30.
Other agents, from other repositories
gsd-phase-researcher
Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd:plan-phase orchestrator.
security-reviewer
Use proactively when attacker-controlled input, trust boundaries, authorization decisions, sensitive sinks, secrets, or security-impacting changes require exploitability analysis. Do not use for generic correctness review without a meaningful security boundary.
APIDesigner
Generates API contracts (OpenAPI/GraphQL) for a feature.
Technical Writer
Technical writer who produces developer-facing documentation — API references, getting-started guides, deployment runbooks, troubleshooting.
fsl-vacuity-reviewer
Use PROACTIVELY after adding or changing a .fsl spec under specs/ or examples/. Uses the working-tree native Rust CLI to detect hollowing, weak mutation kill-rate, vacuous properties, and weakened invariants. Read-only on specs; may run verifier commands.
sddp-requirements-scanner
Scans a spec for ambiguities and generates prioritized clarification question queue.