tools-setup

tools-setup is a skill for Claude Code from Cognigy/cognigy-plugin. It costs 49 tokens per session (4,242 once invoked), scanned A, original, MIT.

A guide for adding tools to a Cognigy AI Agent. Tools let an agent call APIs, run custom logic, send email, connect to MCP services, or search a knowledge source.

In plain words
What is it for?
Use it to create and configure tool, HTTP, MCP, knowledge, or email tools, define their inputs and responses, and test them with the agent.
Why use it?
It explains which tool type to choose and how to configure it so the tool is connected to the agent’s conversation flow.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the cognigy plugin — 16 skills, 2 agents shipped together

Good fit Use it to create and configure tool, HTTP, MCP, knowledge, or email tools, define their inputs and responses, and test them with the agent.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cognigy/cognigy-plugin/tools-setup
Install

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.

Any agent
npx skills add Cognigy/cognigy-plugin --skill tools-setup
Clone the repo
git clone --depth 1 https://github.com/Cognigy/cognigy-plugin

Made for: Claude Code.

Or install cognigy, the plugin that ships this one along with the rest of its 16 skills, 2 agents.

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 tools-setup

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/cognigy/cognigy-plugin/tools-setup"><img src="https://agentmods.dev/badge/skills/cognigy/cognigy-plugin/tools-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,242 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 warn 7 Sept 2026
SkillSpector: 3 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Data Exfiltration · line 148
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 284
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 167
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00049 $0.04242
Opus 5.5 $0.00020 $0.01697
Sonnet 5.5 $0.00010 $0.00848
Haiku 4.5 $0.00005 $0.00424

Measured 14d ago against content hash 3ddcade1e893, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

tools-setup 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 14d 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.

plugin/skills/tools-setup/SKILL.md · 360 lines

How it starts

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

Adding Tools to an AI Agent

What are tools?

Tools give an AI Agent capabilities beyond conversation — calling APIs, executing code, or searching knowledge bases. Without tools, an agent can only chat.

Steps

  1. Create the agent first: create_ai_agent { projectId, name, description } (create_tool requires an agent with an auto-provisioned flow)
  2. create_tool { aiAgentId, toolType, name, config }
  3. The tool is automatically wired into the agent's flow
  4. Test with talk_to_agent

Rule of thumb: each tool in an agent flow should have a unique toolId. If you need more logic, parameters, validation, or HTTP calls for that tool, add them inside the same tool branch instead of creating another tool with the same toolId.

Parameter schema rules (config.parameters)

parameters is a JSON Schema string that Cognigy passes VERBATIM to the LLM provider. create_tool / update_tool validate it and reject violations, because a broken schema either fails every conversation turn with a provider 400 (strict models) or is silently dropped (the tool is called with no arguments). The contract:

  • Top level: {"type":"object","properties":{...},"required":[...]} — required is mandatory (use [] if nothing is required).
  • EVERY property needs "type" AND "description". Allowed types: string, number, integer, boolean, object, array, null.
  • array properties need "items". Nested objects with "properties" also need their own "required".
  • "additionalProperties": false is injected automatically at every object level.
  • Strict-mode models (OpenAI Responses API, e.g. gpt-5.x, where strict is forced on): list EVERY property key in required; make a parameter optional with a nullable type — {"type":["string","null"],"description":"..."}. Non-strict providers ignore this, so it is the safe default.
  • Nested object properties and integer are valid at runtime but not renderable by the Cognigy UI's graphical parameter builder — the node's Parameters section then shows the raw JSON editor. That is cosmetic; prefer flat schemas when you don't need nesting.

Read the full file on GitHub · 360 lines

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. 14d ago Changed · +9 lines · +9 tokens per session 3ddcade1e893
  2. 28d ago Changed · +20 lines · +4 tokens per session 8d3139d46eef
  3. 1mo ago Changed · +22 lines 7f7f4d04546c
  4. 2mo ago Changed · +11 lines c60f2f6e5e12
  5. 2mo ago First seen · 298 lines · 36 tokens per session scan A 710f6e9b0210

Subscribe to this mod's changes

tools-setup is a skill published in the GitHub repository Cognigy/cognigy-plugin (18 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 4,242 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-31.

Related

tools-setup compared with skills from other repositories

tools-setup next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
tools-setupCognigy/cognigy-pluginSkill18yesterdayMITA49Claude Code
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code