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 commands/aegntic/cldcde/create-workflowgit clone --depth 1 https://github.com/aegntic/cldcdeWhat 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.00138 |
| Opus 5 | $0.00000 | $0.00069 |
| Sonnet 5 | $0.00000 | $0.00028 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
create-workflow 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.
What it actually says
Generate an n8n workflow JSON from a natural language description of the automation.
Steps
- Parse the automation description:
- Design the workflow node graph:
- Generate the n8n workflow JSON:
- Add error handling:
- Add workflow metadata:
- Test the workflow structure for validity.
- Provide setup instructions for required credentials.
Format
{
"name": "<workflow name>",
"nodes": [...],
"connections": {...},
Rules
- Use the latest n8n node types and API formats.
- Include credential placeholders, never hardcode secrets.
- Add error handling nodes for production workflows.
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 · 31 lines · 0 tokens per session scan A 540e008adbb1
create-workflow is a command published in the GitHub repository aegntic/cldcde (11 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 138 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-30.
Other commands, from other repositories
seed
Load fixture teams + products into the local D1 database.
smoke
Deploy a versioned preview, hit smoke endpoints, print a status table.
migrate
Apply pending D1 migrations to local (default) or remote.
deploy-preview
Build + deploy a versioned preview; print the preview URL.
scriptwriter-draft
Create a writers' room with a seed prompt and (optionally) contribute the first scene. Co-brainstorm space with signed contributions and a live SSE stream for peers.
scriptwriter-draw
Draw a random chaos card from the 13-card deck — a plot-twist prompt the user can use as a scene seed, a basistext for an RRR cascade, or a riff for a room contribution.