Blacknode: Skill for Codex

.agents/skills/blacknode-development/SKILL.md

blacknode-development is a skill for Codex from temiroff/Blacknode. It costs 103 tokens per session (1,985 once invoked), scanned A, original, Apache-2.0.

A development guide for Blacknode, a Python and Rust system with an editor, package manager, workflow nodes, and extension packages.

In plain words
What is it for?
Use it to change Blacknode’s runtime, server, editor, packages, exporters, or node contracts; create reusable nodes and extensions; and test or document those changes.
Why use it?
It helps you choose the correct part of the system to change while keeping existing saved workflows working and checking that changes behave correctly.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md.

This is temiroff/Blacknode's own configuration. It tells Codex how to work on Blacknode itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Blacknode configures →

Reuse

Borrowing it

Nothing to install: this file belongs to temiroff/Blacknode. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/temiroff/Blacknode/master/.agents/skills/blacknode-development/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/temiroff/Blacknode

Made for: Codex.

Wrote 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.

agentmods badge for blacknode-development

README.md
[![agentmods](https://agentmods.dev/badge/skills/temiroff/blacknode/blacknode-development/github.svg)](https://agentmods.dev/skills/temiroff/blacknode/blacknode-development)
Your own site
<a href="https://agentmods.dev/skills/temiroff/blacknode/blacknode-development"><img src="https://agentmods.dev/badge/skills/temiroff/blacknode/blacknode-development/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.

agentmods 80×15 button for blacknode-development

Your own site · 80×15
<a href="https://agentmods.dev/skills/temiroff/blacknode/blacknode-development"><img src="https://agentmods.dev/badge/skills/temiroff/blacknode/blacknode-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 103 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,985 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00103 $0.01985
Opus 5.5 $0.00041 $0.00794
Sonnet 5.5 $0.00021 $0.00397
Haiku 4.5 $0.00010 $0.00198

Measured 2mo ago against content hash d8615931dd60, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

blacknode-development 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 2mo 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.

.agents/skills/blacknode-development/SKILL.md · 202 lines

How it starts

The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Blacknode Development

Develop the smallest reusable layer that owns the requested capability, protect saved-workflow compatibility, and prove the result through both focused tests and a representative workflow when applicable.

Start Here

  1. Read the nearest AGENTS.md; package repositories have scoped guidance.
  2. Inspect the current implementation, tests, and public documentation before choosing a layer.
  3. Check Git status in the exact worktree being changed. packages/* are independent repositories, not tracked children of the core repository.
  4. Decide whether the capability belongs in core, an extension package, a user-local custom node, or a workflow-local PythonFn.
  5. For a hardware, transport, simulation, or replay provider, read docs/provider-authoring.md and inspect the live capability contract.
  6. Implement the narrowest coherent change, add tests, and update public docs.
  7. Build a small workflow/template when it materially proves discovery, ports, runtime behavior, or package resolution.

Choose the Ownership Layer

Need Put it here
Graph types, execution, validation, registry, CLI, MCP, exporters python/blacknode/
Browser/editor behavior or UI editor/
Editor HTTP API, runtime services, replay editor-server/
Portable Rust graph/runtime/CLI behavior crates/
Broad, dependency-light node python/blacknode/nodes/
Hardware, GPU, ROS, vision, or large optional dependency extension package
User-owned local reusable behavior custom-nodes/
One graph's small adapter PythonFn in the workflow

Do not duplicate a domain implementation in core and a package. Keep the core contract generic and place transport- or hardware-specific implementations behind package nodes and runtime adapters.

Preserve Hardware Replaceability

  • Keep base robot contracts, profiles, and capability inspection functional with no vendor driver, sensor SDK, ROS installation, simulator, or accelerator package installed. Missing providers return a structured unavailable state and do not prevent unrelated capabilities from loading.
  • Make applications, skills, planners, and controllers consume stable capability contracts rather than vendor SDKs, device paths, transports, or component implementations.
  • Bind capability providers through robot profiles and component configuration. A compatible camera, LiDAR, actuator bus, simulator, or compute-provider swap must preserve mission logic, workflow connections, and semantic node names.
  • Bind calibration, limits, and sensor extrinsics to stable physical identity, not merely a component or driver type.
  • Supply a mock or replay provider for every hardware capability. Do not claim providers are interchangeable until the same contract suite passes against the mock and every supported provider.

Read the full file on GitHub · 202 lines

Files

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.

Changes

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.

  1. 2mo ago First seen · 202 lines · 103 tokens per session scan A d8615931dd60

Subscribe to this mod's changes

blacknode-development is a skill published in the GitHub repository temiroff/Blacknode (23 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 103 tokens to every session and 1,985 once invoked, about $0.0004 per session on Opus 5.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.

Related

blacknode-development compared with skills from other repositories

blacknode-development next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
blacknode-developmenttemiroff/BlacknodeSkill231mo agoApache-2.0A103Codex
django-patternsaffaan-m/ECCSkill298k4d agoMITA32Claude Code, Kiro
fastapi-patternsaffaan-m/ECCSkill298k4d agoMITA35Claude Code, Kiro
rust-gatewayBerriAI/litellmSkill63kyesterdaynoneA70Claude Code, Codex
flask-expertpersonamanagmentlayer/pclSkill4411d agoApache-2.0A49Claude Code
plugin-systemellmos-ai/skillsSkill94d agoMITA27Claude Code, Codex
accelerateNousResearch/hermes-agentSkill261kyesterdayMITA13Claude Code, Codex