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 skills add takeshy/obsidian-llm-hub --skill add-workflow-nodegit clone --depth 1 https://github.com/takeshy/obsidian-llm-hubWrote 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.
[](https://agentmods.dev/skills/takeshy/obsidian-llm-hub/add-workflow-node)<a href="https://agentmods.dev/skills/takeshy/obsidian-llm-hub/add-workflow-node"><img src="https://agentmods.dev/badge/skills/takeshy/obsidian-llm-hub/add-workflow-node/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.
<a href="https://agentmods.dev/skills/takeshy/obsidian-llm-hub/add-workflow-node"><img src="https://agentmods.dev/badge/skills/takeshy/obsidian-llm-hub/add-workflow-node.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00040 | $0.00445 |
| Opus 5.5 | $0.00016 | $0.00178 |
| Sonnet 5.5 | $0.00008 | $0.00089 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
add-workflow-node 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.
This is a copy
100% identical to add-workflow-node — 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.
What it actually says
Add New Workflow Node Type
Add a new workflow node type called $ARGUMENTS to the plugin.
Required File Changes (ALL must be updated)
Update the following files in order. Missing any file will cause bugs:
1. src/workflow/types.ts
- Add to
WorkflowNodeTypeunion type - Add to
WORKFLOW_NODE_TYPESSet (single source of truth forisWorkflowNodeType()) - If forgotten: nodes are skipped during parsing and disappear from visual workflow
2. src/workflow/workflowSpec.ts
- Add documentation entry for AI workflow generation
3. src/workflow/nodeHandlers.ts
- Add
handle*Node()function with the node's execution logic - Export the handler
4. src/workflow/executor.ts
- Add
casein the switch statement to call the handler and log execution - If forgotten: node execution fails silently
5. src/ui/components/workflow/WorkflowPanel.tsx
- Add to
NODE_TYPE_LABELSobject (display name) - Add to
ADDABLE_NODE_TYPESarray - Add to
getDefaultProperties()switch (default property values) - Add to
getNodeSummary()switch (summary text for node list)
6. src/ui/components/workflow/NodeEditorModal.ts
- Add to
NODE_TYPE_LABELSobject - Add
caseinrenderPropertyFields()switch for editor UI fields
Verification
After implementing all changes:
- Run
npm run lintto check for errors - Run
npm run buildto verify compilation - Review each file to ensure the new node type is consistently named
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 · 49 lines · 40 tokens per session scan A 8488c6ac2cb4
add-workflow-node is a skill published in the GitHub repository takeshy/obsidian-llm-hub (38 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 445 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to add-workflow-node, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
execute
Execute an approved Maestro implementation plan using the shared session-state contract.
orchestrate
Run the full Maestro workflow for complex engineering tasks that need a mandatory design dialogue, approved implementation plan, and then execution with shared session state.
resume-session
Resume an interrupted Maestro session using the existing active-session file and shared phase tracking.
security-audit
Run a Maestro-style security assessment for authentication, authorization, data exposure, secret handling, and exploitability risks.
seo-audit
Run a Maestro-style SEO assessment for meta tags, structured data, crawlability, and Core Web Vitals.
status
Summarize the active Maestro session without mutating state.