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/claude-plugins/tendgit 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.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 yesterday.
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 tend — 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 — 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.
- yesterday First seen · 125 lines · 90 tokens per session scan A 95728ed82ba9
tend is an agent published in the GitHub repository juxt/claude-plugins (10 stars, last pushed 4d 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. It is 100% identical to tend, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.