A workflow for writing and maintaining Allium specification files, which describe software behavior through entities, rules, triggers, interfaces, and contracts.

It supports adding, editing, clarifying, restructuring, fixing, renaming, refactoring, and migrating Allium specifications.

It helps developers make precise specification changes, validate their syntax, and avoid guessing when a requirement is unclear.

tend — Skill for Claude Code by juxt/allium

Install

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.

Any agent

npx skills add juxt/allium --skill tend

Clone the repo

git clone --depth 1 https://github.com/juxt/allium

Made for: Claude Code.

Or install allium, the plugin that ships this one along with the rest of its 7 skills, 5 agents, 2 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/juxt/allium/tend/github.svg)](https://agentmods.dev/skills/juxt/allium/tend)

Your own site

<a href="https://agentmods.dev/skills/juxt/allium/tend"><img src="https://agentmods.dev/badge/skills/juxt/allium/tend/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/juxt/allium/tend"><img src="https://agentmods.dev/badge/skills/juxt/allium/tend.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 90 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,223 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

Socket pass 15 Sept 2026
Snyk pass 15 Sept 2026
NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00090	$0.02223
Opus 5.5	$0.00036	$0.00889
Sonnet 5.5	$0.00018	$0.00445
Haiku 4.5	$0.00009	$0.00222

Measured 1mo ago against content hash 631e5a253509, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

tend — 100% identical, 0 lines differ

skills/tend/SKILL.md · 121 lines

How it starts

The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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 tend subagent (for example inside the Allium loop), where no user is reachable. Do not guess an answer: record each question as an open question declaration 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 .allium files (search the project to find them if not specified).
If the allium CLI is available, run allium check against 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 .allium files.

How you work

Challenge vagueness. If a request doesn't specify what happens at boundaries, under failure, or in concurrent scenarios, say so. Ask what should happen rather than inventing behaviour. A spec that papers over ambiguity is worse than no spec. Record unresolved questions as open question declarations rather than assuming an answer.

Read the full file on GitHub · 121 lines

Changes

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 · 121 lines · 90 tokens per session scan A 631e5a253509

Subscribe to this mod's changes

tend is a skill published in the GitHub repository juxt/allium (513 stars, last pushed 20d ago), licensed MIT. It adds 90 tokens to every session and 2,223 once invoked, about $0.0004 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-08-30.

Writing and docs ai-agent-tools behaviour-driven-development formal-methods spec-driven-development

r3f-animation

React Three Fiber animation - useFrame, useAnimations, spring physics, keyframes. Use when animating objects, playing GLTF animations, creating procedural motion, or implementing physics-based movement.

zebbern/claude-code-guide · 43 tokens

r3f-best-practices

React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.

zebbern/claude-code-guide · 74 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

tend