Tool Registration

What it does

When your agent uses it

• Tasks that involve Third-party API integration

Example prompts

• “/tool-registration”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

1. 1Notify the orchestrator so it can update its own TOOLS.md if the tool is org-wide
2. 2If it is a shared tool all agents should have, the orchestrator should broadcast to all agents.

What it can do on your machine

Read from SKILL.md and the folder at commit 6f93838. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and bash).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Tool Registration loads about 734 tokens when it runs. Until then it costs about 134 tokens; SKILL.md has 176 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~134

When it runs · the whole SKILL.md, loaded when a task matches

~734

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from grandamenium/cortextos at commit 6f93838, republished under its MIT licence (© grandamenium). 176 words, ~734 tokens.

name

tool-registration

description

A new tool has been added to the system and is not yet documented — agents do not know it exists or how to use it. This includes any new bus script, CLI binary, MCP server, external web tool or API wrapper, or any other capability an agent can invoke. You need to add it to TOOLS.md with its command, purpose, key flags, and usage examples. Or you have discovered that TOOLS.md is out of sync with what is actually available. This keeps the tool reference current so every agent can discover and use new capabilities.

triggers

new tool, register tool, add tool, document tool, tools.md, missing from tools, tool not documented, new script, new command, new binary, new capability…

orgs/{org}/agents/{agent}/TOOLS.md

### new-command
Brief description of what it does.

```bash
cortextos bus new-command <required_arg> [--optional flag]

cortextos bus new-command "my value" --flag result

Also add it to the Quick Reference table at the bottom of TOOLS.md:
```markdown
| I need to...         | Command              |
|----------------------|----------------------|
| Do the new thing     | `new-command`        |

### ToolName (purpose)
- **Binary**: `toolname`
- **Use for**: What tasks it handles
- **Auth**: How to authenticate
- **Usage examples**:
  - `toolname command --flag value`
  - `toolname other-command`
- **Important**: Any gotchas or constraints

cortextos bus send-message "$CTX_ORCHESTRATOR_AGENT" normal "New tool registered in TOOLS.md: <tool name>. Update your TOOLS.md if applicable."

© grandamenium, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in community/agents/security/.claude/skills/tool-registration of grandamenium/cortextos.

Open the folder on GitHubat commit 6f93838