Borrowing it
Nothing to install: this file belongs to AutomatosAI/automatos-ai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AutomatosAI/automatos-ai/main/.claude/skills/register-tool/SKILL.mdgit clone --depth 1 https://github.com/AutomatosAI/automatos-aiWrote 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/automatosai/automatos-ai/register-tool)<a href="https://agentmods.dev/skills/automatosai/automatos-ai/register-tool"><img src="https://agentmods.dev/badge/skills/automatosai/automatos-ai/register-tool/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/automatosai/automatos-ai/register-tool"><img src="https://agentmods.dev/badge/skills/automatosai/automatos-ai/register-tool.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.00045 | $0.00372 |
| Opus 5.5 | $0.00018 | $0.00149 |
| Sonnet 5.5 | $0.00009 | $0.00074 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
register-tool 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 25d 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
Register Platform Tool
Slash command: /register-tool <tool_name> (e.g. /register-tool platform_export_workspace)
orchestrator/modules/tools/README.md, section "Adding a platform action", is the current pattern: a definition in discovery/actions_<domain>.py, its handler in discovery/handlers_<domain>.py, and a test under modules/tools/tests/. Read it first and follow an existing pair such as actions_blog.py / handlers_blog.py.
Before writing code
grep -rn "<tool_name>" orchestrator/modules/tools/discovery/— a match means you are extending, not registering. Prefer extending an existing action over adding a near-duplicate.- Settle the contract: the inputs, the result shape (
{"success": True, "data": ...}or{"success": False, "error": ...}), the side effects, and the permission level (requires_confirmation=Truefor anything destructive).
The description is the contract
The model picks and calls the action from its description and parameter schema alone. Say what it does, when to use it and when not to, what each parameter means and what it does not return; every enum value must be one the handler accepts. Write it plainly: no MUST/ALWAYS boosters, and no worked examples or call transcripts in the text.
Verify
CI is the gate; nothing runs on this machine. The test goes under modules/tools/tests/; push and let CI run it.
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.
- 25d ago Changed · -68 lines · +3 tokens per session 93346b372fdf
- 1mo ago First seen · 93 lines · 42 tokens per session scan A 95c21c4d3951
register-tool is a skill published in the GitHub repository AutomatosAI/automatos-ai (74 stars, last pushed today), licensed Apache-2.0. It adds 45 tokens to every session and 372 once invoked, about $0.0002 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.
Other skills, from other repositories
knowledge-org
A guide to organising large bodies of knowledge so an AI system can navigate relationships, summaries, and layers instead of searching only flat text chunks. It covers tree indexes, knowledge graphs, file-like structures, incremental updates, and long-term memory layouts.
rag-pipeline
A guide to RAG, a method where a system retrieves relevant passages from an external knowledge base before an AI model writes an answer. It covers splitting documents, searching by meaning or exact words, combining results, and measuring retrieval quality.
setup-open-index
Install and configure Open Index as the read/write context layer for a domain-specialized agent. Use when setting up a legal, marketing, customer support, sales, infrastructure, or other domain agent with Open Index over MCP.
remake-deck
Remake a company's source pitch deck (PDF, PPTX, or folder of slide images) into N clean-room design variants that play in the DidiDecks Scroll-UI shell. The agent takes the VP Eng / orchestrator role and runs the dididecks-ai plan Remake-Source-Deck-into-Design-Variants, which extracts and audits the deck, fans out N…
go4
Use when designing, architecting, planning, or debugging any system with an LLM in it — agents, agent loops, RAG and retrieval, prompt pipelines, multi-agent or subagent orchestration, tool use and MCP, memory and context management, evals, or production guardrails. Trigger BEFORE committing to an approach — choosing…
rag-pipelines
Best practices for Retrieval-Augmented Generation (RAG) pipelines. Use when working with vector databases, embeddings, chunking strategies, semantic search, or hybrid search architectures.