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 agentmods add skills/cognigy/cognigy-plugin/agent-creationnpx skills add Cognigy/cognigy-plugin --skill agent-creationgit clone --depth 1 https://github.com/Cognigy/cognigy-pluginWrote 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/cognigy/cognigy-plugin/agent-creation)<a href="https://agentmods.dev/skills/cognigy/cognigy-plugin/agent-creation"><img src="https://agentmods.dev/badge/skills/cognigy/cognigy-plugin/agent-creation.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.00049 | $0.02157 |
| Opus 5 | $0.00024 | $0.01078 |
| Sonnet 5 | $0.00010 | $0.00431 |
| Haiku 4.5 | $0.00005 | $0.00216 |
Grade A, and why
agent-creation 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building a Cognigy AI Agent
Prerequisites
- A project (use list_resources { resourceType: "project" } to find one, or let create_ai_agent create one)
- A working LLM resource in the target project before testing the agent
Steps
- list_resources { resourceType: "project" } — inspect all projects
- Choose the target project
- If it already exists: use its projectId
- If the user wants a new project: call create_ai_agent without projectId, keep the returned projectId, and if llmStatus is "unknown" continue with the LLM reuse steps below before testing the agent
- Run list_resources { resourceType: "llm_model", projectId } — check whether the target project already has a reusable LLM with a non-empty connectionId
- If the target project has no reusable LLM, check the other projects for reusable LLMs
- Run list_resources { resourceType: "llm_model", projectId } for each other project
- Choose only candidates whose llm_model has a non-empty connectionId
- Do not treat an LLM without connectionId as a valid reuse candidate
- If another project already has a reusable LLM, transfer the required model set together with its connection resource(s):
- manage_packages { operation: "list_exportable", projectId: "" }
- If this workflow will use knowledge, identify the source project's exact Knowledge Search model and embedding model before exporting anything
- manage_packages { operation: "export", projectId: "", resourceIds: ["", "", ""], name: "llm-transfer" }
- manage_packages { operation: "upload_and_inspect", projectId: "", filePath: "" }
- manage_packages { operation: "import", projectId: "", packageId: "" }
- list_resources { resourceType: "llm_model", projectId: "" } — verify the required models are present before testing or continuing setup
- Only if no reusable LLM with connectionId exists, or the package transfer failed: setup_llm { projectId, provider: "openAI", modelType: "gpt-4o", apiKey }
- With isDefault: true (the default), agents auto-use this LLM — no extra step needed.
- Save the
referenceIdfrom the response if you need to assign it explicitly later. (See the llm-providers skill for valid provider/modelType values)
- create_ai_agent { projectId, name, description } — Returns: agent, flow, endpoint, endpointUrl — The default LLM is automatically assigned to the agent's job node. If llmStatus is "configured", no extra step is needed.
- (Only if llmStatus is "unknown" after create) Do not test yet. First repeat steps 4-6 for the returned projectId, then assign LLM to agent if needed: update_ai_agent { aiAgentId, jobConfig: { llmProviderReferenceId: "<referenceId from step 4 or 5>" } }
- Only after the project has a confirmed working LLM: talk_to_agent { endpointUrl, message }
- Refine the agent using update_ai_agent — see "All configuration fields" below
- Repeat 9-10 until satisfied
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.
- 6d ago First seen · 117 lines · 49 tokens per session scan A 833f251be72e
agent-creation is a skill published in the GitHub repository Cognigy/cognigy-plugin (12 stars, last pushed 3d ago), licensed MIT. It adds 49 tokens to every session and 2,157 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…