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/nonlinear-xyz/factory-kit/llm-workflow-engineergit clone --depth 1 https://github.com/nonlinear-xyz/factory-kitWhat 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.00102 | $0.00176 |
| Opus 5 | $0.00051 | $0.00088 |
| Sonnet 5 | $0.00020 | $0.00035 |
| Haiku 4.5 | $0.00010 | $0.00018 |
Grade A, and why
llm-workflow-engineer 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 3d 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
Apply the preloaded factory-llm-workflow-engineer skill to the delegated task. The canonical skill is the complete workflow and source of truth.
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.
- 3d ago First seen · 11 lines · 102 tokens per session scan A 312ebcc0075f
llm-workflow-engineer is an agent published in the GitHub repository nonlinear-xyz/factory-kit (9 stars, last pushed 29d ago), licensed MIT. It adds 102 tokens to every session and 176 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-31.
Other agents, from other repositories
claude-wiki-pages-onboarding-agent
Guided first-run executor. Walks a brand-new user from a fresh project to a working, queryable wiki — health check → scaffold → add a source → ingest (git-checkpointed auto-heal) → first cited answer — one step at a time, with a plain-language explanation after each. Invoked by the claude-wiki-pages-orchestrator-agent…
ai-ml
AI/ML 통합 전문가 + LLM API 최신 모델/SDK 코딩 가이드. RAG 시스템, 문서 분석, OpenAI/Anthropic/Gemini/Ollama 최신 API 보장. "AI integration", "RAG search", "LLM service", "OpenAI", "Anthropic", "Gemini", "Ollama" 요청에 실행.
rag-specialist
Expert consultant for retrieval-augmented generation, knowledge bases, intelligent document processing, and semantic search systems. Use proactively for RAG architecture analysis, knowledge system design, document processing strategies, and semantic search optimization. Provides consultation and recommendations only …
vision
Senior AI Engineer — LLMs, autonomous agents, RAG, fine-tuning, model evaluation, AI integrations. Call to design and implement any artificial intelligence-based system.
AI Specialist
Expert in integrating LLMs, building RAG systems (pgvector), and creating MCP servers.
ai-engineer
An AI engineer who builds production applications powered by LLMs — designing RAG pipelines, agent architectures, tool use patterns, and evaluation frameworks. Distinct from ML engineer (who trains models) — focuses on integrating and orchestrating AI capabilities. Use for LLM application architecture, RAG design…