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 core0-io/nio --skill nio-configgit clone --depth 1 https://github.com/core0-io/nioWrote 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/core0-io/nio/nio-config)<a href="https://agentmods.dev/skills/core0-io/nio/nio-config"><img src="https://agentmods.dev/badge/skills/core0-io/nio/nio-config.svg" alt="Measured on agentmods" 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.00071 | $0.00665 |
| Opus 5 | $0.00036 | $0.00332 |
| Sonnet 5 | $0.00014 | $0.00133 |
| Haiku 4.5 | $0.00007 | $0.00067 |
Grade A, and why
nio-config 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 8d 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
Nio — Configuration
View or update the Nio configuration. This is the focused config capability of the Nio framework. Configuration lives at ~/.nio/config.yaml (or $NIO_HOME/config.yaml).
Passive invocation. If the user asks to see their Nio config, check/change the protection level, or reset config, you MUST use the CLI below rather than describing settings from memory.
Resolving the Script Path
The CLI for this skill lives in the sibling nio skill, not in this skill's own directory:
- This SKILL.md's parent directory is THIS skill's directory (e.g.
<plugins>/skills/nio-config/). - The script is the sibling
nioskill'sscripts/config-cli.js— i.e.../nio/scripts/config-cli.jsrelative to this directory. Derive the absolute path; do not hard-code~/.claude/.... - Invoke with a single
nodecommand — nocd, no;/&&/|/$(...)/backticks.
Routing
| Input | Action |
|---|---|
config, show, or empty |
Run node ../nio/scripts/config-cli.js show and present the JSON |
strict / balanced / permissive |
Read ~/.nio/config.yaml, update only guard.protection_level (preserve all other settings), write back, confirm to the user |
reset |
Run node ../nio/scripts/config-cli.js reset |
Protection Levels
| Level | allow | confirm | deny | Behaviour |
|---|---|---|---|---|
strict |
0 – 0.5 | — | 0.5 – 1.0 | Block all risky actions |
balanced (default) |
0 – 0.5 | 0.5 – 0.8 | 0.8 – 1.0 | Block dangerous, confirm risky — good for daily use |
permissive |
0 – 0.9 | — | 0.9 – 1.0 | Only block critical threats |
For the full field reference (guard / collector sections, external_analyser, permitted/blocked tools, etc.) see the unified /nio config documentation. Set NIO_HOME to change the config directory (default: ~/.nio).
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.
- 8d ago First seen · 44 lines · 71 tokens per session scan A 96abb8358fb4
nio-config is a skill published in the GitHub repository core0-io/nio (19 stars, last pushed 17d ago), licensed Apache-2.0. It adds 71 tokens to every session and 665 once invoked, about $0.0004 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
titanclip
Interact with the TitanClip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any TitanClip API endpoint. Do NOT use for…
titanclip-create-agent
Create new agents in TitanClip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hire request.
para-memory-files
File-based memory system using Tiago Forte's PARA method. Use this skill whenever you need to store, retrieve, update, or organize knowledge across sessions. Covers three memory layers: (1) Knowledge graph in PARA folders with atomic YAML facts, (2) Daily notes as raw timeline, (3) Tacit knowledge about user patterns.…
titanclip-create-plugin
Create new TitanClip plugins with the current alpha SDK/runtime. Use when scaffolding a plugin package, adding a new example plugin, or updating plugin authoring docs. Covers the supported worker/UI surface, route conventions, scaffold flow, and verification steps.
compare-harnesses
Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.
example-harness
Scaffold a ready-made AI agent harness in one command from the 19 published @metaharness/ example packages — 9 host integrations (Claude Code, Codex, Hermes, pi.dev, OpenClaw, RVM, Copilot, OpenCode, GitHub Actions) + 10 vertical pods (devops, research, trading, support, legal, coding, education, sales, gaming…