Agentic Tool Integration logo

Agentic Tool Integration

CommunityPopular
samugit83
agentic-tool-integration

Wiring a new tool the AI agent can call (not the recon pipeline): the tool registry, the phase map, the hardcoded dispatch chokepoint, and the duplicated execution paths that make a tool work in single mode but silently break in parallel plans. Trigger: adding or editing a tool the agent invokes; editing agentic/prompts/tool_registry.py, PhaseAwareToolExecutor in agentic/tools.py, agentic/orchestrator_helpers/nodes/execute_tool_node.py or execute_plan_node.py, TOOL_PHASE_MAP / DANGEROUS_TOOLS in agentic/project_settings.py, or a new MCP server in mcp/servers/.

Overview

Publishersamugit83
Repositoryredamon
Skill nameagentic-tool-integration
Stars
2.5K
Forks
504
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by samugit83 on GitHub. Read the source before you install it.

Installation

Install the Agentic Tool Integration AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/samugit83/redamon.git /tmp/redamon
mkdir -p .claude/skills
cp -r /tmp/redamon/skills/agentic-tool-integration .claude/skills/agentic-tool-integration
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Agentic Tool Integration in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Agentic Tool Integration on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Agentic Tool Integration is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

When to Use

  • Adding any tool the agent uses during a chat session (CLI wrapper, MCP tool, or API tool).

For a recon-pipeline tool (runs during a scan, writes the graph), use recon-tool-integration instead. For the per-setting/default multi-layer wiring, use project-settings-cascade. For a whole new attack skill (not a tool), use builtin-agent-skill.


Critical Rules

  • NEVER import a package not already in the agent image. agentic/ is baked into the redamon-agent image; a missing import crash-loops the container. Confirm it is in agentic/requirements.txt or the Dockerfile first.
  • NEVER add a tool without a TOOL_REGISTRY entry in agentic/prompts/tool_registry.py. The registry is the single source of truth the LLM reads; an unregistered tool is invisible to the agent. All four fields (purpose, when_to_use, args_format, description) are required, and the description must clear the 100-char minimum in agentic/tests/test_tool_registry_completeness.py, which fails on any unregistered or stub entry.
  • NEVER forget the dispatch branch for a non-MCP / API tool. PhaseAwareToolExecutor.execute() at agentic/tools.py:2070 has hardcoded if/elif dispatch. A Type D (API) tool or an MCP tool needing key injection MUST add an elif; without it the tool is registered but never dispatched. MCP tools with no key injection go through the else branch automatically.
  • NEVER edit execute_tool_node.py without mirroring it in execute_plan_node.py. execute_tool_node.py (single tool) and execute_plan_node.py (parallel plans) duplicate long-running detection and session/listener handlers. Update one only and the tool works interactively but silently misbehaves in parallel plan execution.
  • NEVER rely on the Prisma default to reach existing projects. The agentToolPhaseMap default applies to NEW projects only. Existing projects need a jsonb UPDATE or the agent never sees the tool there. See project-settings-cascade.
  • ALWAYS add the tool to TOOL_PHASE_MAP in agentic/project_settings.py. If it sends attack traffic: also add it to DANGEROUS_TOOLS (frozenset, project_settings.py:22), a per-tool section in agentic/prompts/stealth_rules.py, and the right list in CATEGORY_TOOL_MAP (_check_roe_blocked, execute_plan_node.py:47).

Pick the integration type (simplest that fits)

TypeUse whenCore files beyond the registry
A kali_shelltool is in Kali, 300s timeout OK, no parsingDockerfile + kali_shell description only (no registry entry)
B MCP tool on existing serverCLI tool, custom timeout/parsing, fire-and-forget@mcp.tool() in an existing mcp/servers/*.py (auto-discovered)
C new MCP serverstateful/interactive, own portnew mcp/servers/*_server.py + SERVERS in run_servers.py + URL in MCPToolsManager
D API/HTTP toolexternal API, key-gatedToolManager class + elif dispatch in tools.py + orchestrator key hot-reload

Naming is uniform across every layer: MCP fn / registry key / phase-map key = execute_<tool>; Prisma field camelCase; Python setting SCREAMING_SNAKE; DB column snake_case via @map().

Commands

bash
docker compose build agent && docker compose up -d agent   # mandatory: agentic/ is baked
docker compose exec webapp npx prisma db push              # if you added a Prisma field (NEVER prisma migrate)
./agentic/run_tests.sh                                     # gate; includes the registry completeness test

Resources

Frequently asked questions

What does the Agentic Tool Integration AI skill do?

Wiring a new tool the AI agent can call (not the recon pipeline): the tool registry, the phase map, the hardcoded dispatch chokepoint, and the duplicated execution paths that make a tool work in single mode but silently break in parallel plans. Trigger: adding or editing a tool the agent invokes; editing agentic/prompts/tool_registry.py, PhaseAwareToolExecutor in agentic/tools.py, agentic/orchestrator_helpers/nodes/execute_tool_node.py or execute_plan_node.py, TOOL_PHASE_MAP / DANGEROUS_TOOLS in agentic/project_settings.py, or a new MCP server in mcp/servers/.

Why use Agentic Tool Integration on TypingMind?

Because you install it once and use it with any model. Agentic Tool Integration is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Agentic Tool Integration in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/samugit83/redamon/tree/master/skills/agentic-tool-integration. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Agentic Tool Integration?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Agentic Tool Integration?

As many as you like. As long as a model supports skills, you can use Agentic Tool Integration with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Agentic Tool Integration AI skill free?

Yes. It is published on GitHub by samugit83 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇