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/dimpagk92/cellar/n8ngit clone --depth 1 https://github.com/dimpagk92/cellarWhat 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.00000 | $0.01640 |
| Opus 5 | $0.00000 | $0.00820 |
| Sonnet 5 | $0.00000 | $0.00328 |
| Haiku 4.5 | $0.00000 | $0.00164 |
Grade A, and why
n8n 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Driving CEL from n8n
This page shows how to drive CEL from n8n.
Read docs/adapters-cel-agents.md first if you haven't.
Purpose
n8n is a workflow automation platform. It does not speak MCP natively, so CEL needs a bridge. Two paths:
- Execute Command node →
cellarCLI. Works today. Each step is a shell invocation. Good for deterministic, short workflows. - HTTP Request node →
cellar-worker. Planned. Uses the Phase 1 worker protocol (docs/worker-protocol.md). Good for long-running goals and remote execution. Not yet shipped — tracked on the roadmap.
This document covers both. Path 1 is usable now.
Ownership
- n8n owns: the workflow graph, branching, error routing, retries, and scheduling.
- CEL owns: execution of each goal or action.
- Adapters own: app-specific truth (Numbers cells etc.).
Because n8n is a workflow engine, not an LLM agent, it typically either:
- (a) hands CEL a full natural-language goal and lets
cel_think run_goaldrive autonomously, or - (b) hands CEL discrete actions produced by some upstream LLM node (e.g. an OpenAI node) and composes them with
cel_act.
Mode (a) is the simplest integration and is what the examples below show.
Path 1: Execute Command → cellar CLI (works today)
Setup
- Build CEL on the machine running n8n:
cd /path/to/cellar && pnpm install && pnpm -r build - Make sure
cellaris on PATH (or reference it by absolute path in the n8n node). - Grant macOS Accessibility permission to whichever process n8n uses to shell out (e.g.
node,docker, or the n8n desktop app). - If you use
cel_think run_goalfrom the CLI, setCEL_LLM_PROVIDER,CEL_LLM_API_KEY, andCEL_LLM_MODELin the n8n environment.
Example n8n Workflow Snippet
Minimal workflow: manual trigger → Execute Command node that runs a CEL goal → Set node that surfaces the result.
{
"nodes": [
{
"parameters": {},
"id": "trigger",
"name": "Manual Trigger",
"type": "n8n-nodes-base.manualTrigger",
"typeVersion": 1,
"position": [240, 300]
},
{
"parameters": {
"command": "cellar run-goal \"Open Numbers and write BTC in A1\" --json"
},
"id": "cel-run",
"name": "CEL Run Goal",
"type": "n8n-nodes-base.executeCommand",
"typeVersion": 1,
"position": [520, 300]
},
{
"parameters": {
"values": {
"string": [
{ "name": "result", "value": "={{ $json.stdout }}" }
]
}
},
"id": "result",
"name": "Result",
"type": "n8n-nodes-base.set",
"typeVersion": 2,
"position": [800, 300]
}
],
"connections": {
"Manual Trigger": { "main": [[{ "node": "CEL Run Goal", "type": "main", "index": 0 }]] },
"CEL Run Goal": { "main": [[{ "node": "Result", "type": "main", "index": 0 }]] }
}
}
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 · 149 lines · 0 tokens per session scan A f1c1b25517f0
n8n is an agent published in the GitHub repository dimpagk92/cellar (4 stars, last pushed 22d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,640 tokens. 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-31.
Other agents, from other repositories
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
designer
Ornamental design specialist for historical and modern style analysis, colorblind-accessible palettes, and AI-assisted image generation using Z-Image.
hatch3r-ui
UI quality specialist — reviews generated UI for WCAG 2.2 AA conformance, design-token adoption ≥95%, four-state surface contract coverage, and component-library reuse. Use when UI is authored or modified.
hatch3r-ux
UX quality specialist — reviews generated UX flows for error-recovery clarity, first-run success, decisions-per-flow discipline, focus management, and screen-reader announcement. Use when UX flows are authored or modified.
ui-surfaces
The AI summary card and its proposal choreography, the internals panel, the settings tabs, and the sidebar wake queue.
ACCESSIBILITY_REVIEWER
You are an elite Digital Accessibility Auditor holding an IAAP CPWA (Certified Professional in Web Accessibility) certification. Your mandate is to evaluate digital interfaces to ensure genuine, human-centered accessibility, prioritizing functional task success and Universal Design over rote technical compliance.