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 skills/temiroff/blacknode/blacknode-workflownpx skills add temiroff/Blacknode --skill blacknode-workflowgit clone --depth 1 https://github.com/temiroff/BlacknodeWhat 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.00093 | $0.03377 |
| Opus 5 | $0.00046 | $0.01688 |
| Sonnet 5 | $0.00019 | $0.00675 |
| Haiku 4.5 | $0.00009 | $0.00338 |
Grade A, and why
blacknode-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 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.
How it starts
The opening of the file, as written. The whole thing — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blacknode Workflow
Blacknode is the visual workflow layer for agent harnesses. Use it when a chat or coding agent needs a typed node graph instead of raw JSON or ad hoc scripts.
Scope
Use this skill for:
- Building a new workflow graph from a user request.
- Loading, validating, or repairing
blacknode.workflowJSON. - Opening a workflow in the running visual editor.
- Running a workflow or template and inspecting the structured event log.
- Exporting or importing a workflow with Python round-trip, LangGraph, CrewAI, AutoGen, Swarm, or NVIDIA Agent Stack.
- Creating NVIDIA NIM, local NIM, RAG, tool-agent, or research-pipeline demos.
- Discovering or installing the extension package required by a workflow.
If no existing node expresses a reusable capability, stop graph construction
and use blacknode-development. After implementing and testing the capability,
return here to integrate it into a validated workflow.
Package-Aware Planning
- Inspect
list_nodesandlist_templatesbefore assuming a node is missing. - Prefer installed core or package nodes over one-off code.
- If a template reports missing nodes, use its
metadata.required_packagesand the package index to identify the package. - Ask before installing third-party package code. An indexed official package may be installed when package installation is part of the user's request.
- Run
blacknode packages listafter installation and resolve declared dependency warnings before cooking affected nodes. - Use
PythonFnonly for workflow-local adapters. Useblacknode-developmentfor reusable nodes or packages.
Outcome-First Workflow Design
- Begin with the requested outcome and build the shortest coherent graph that produces it.
- A tracked template must perform a useful end-to-end task. Do not create templates whose main result is proving a node works, showcasing wiring, smoke testing, or confirming that a dependency is ready.
- Every visible node must materially create, transform, route, persist, deploy, or operate something needed by the final result.
- Do not add checker, test, report, echo, or confirmation nodes as graph padding. The node that owns an operation should validate inputs, preflight dependencies, report progress, and return actionable errors when practical.
- Keep implementation validation in automated tests or untracked local developer workflows rather than turning it into a product template.
- Preserve required physical-motion safety, authorization, cost consent, and destructive-action confirmation. Integrate these controls into the owning action or managed service when possible; keep a separate node when the safety contract must be explicit and reusable.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 319 lines · 93 tokens per session scan A 78a185dab7ed
blacknode-workflow is a skill published in the GitHub repository temiroff/Blacknode (23 stars, last pushed 3d ago), licensed Apache-2.0. It adds 93 tokens to every session and 3,377 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-30.
Other skills, from other repositories
release-notes
Draft concise release notes.
session-rag-eval
Run and debug Chatbox session attachment RAG model evaluation with synthetic and real long-file fixtures.
designer_guide
Guidance for creating and editing designs using the designer tool.
row_bot_status_guide
Guidance for querying and managing Row-Bot's own configuration and logs.
design_creator
Structured workflow for creating professional designs — slide decks, documents, landing pages, app mockups, and motion storyboards.
lynkr
Universal LLM gateway with intelligent routing, Graphify code intelligence, Distill compression, routing telemetry, Code Mode, and 12+ provider support. 60-80% cost reduction for Claude Code, Cursor, and Codex.