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 skills add Cognigy/cognigy-plugin --skill troubleshootinggit 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/troubleshooting)<a href="https://agentmods.dev/skills/cognigy/cognigy-plugin/troubleshooting"><img src="https://agentmods.dev/badge/skills/cognigy/cognigy-plugin/troubleshooting/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/cognigy/cognigy-plugin/troubleshooting"><img src="https://agentmods.dev/badge/skills/cognigy/cognigy-plugin/troubleshooting.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.02168 |
| Opus 5.5 | $0.00018 | $0.00867 |
| Sonnet 5.5 | $0.00009 | $0.00434 |
| Haiku 4.5 | $0.00005 | $0.00217 |
Grade A, and why
troubleshooting 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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Troubleshooting
Agent returns empty response
- Inspect the agent flow and tools first:
- list_resources { resourceType: "tool", aiAgentId }
- duplicate
toolIdvalues can cause failed tool execution and empty responses — this is a flow issue, not an LLM or connection issue; remove the duplicate rather than reconfiguring the LLM
- Check LLM exists: list_resources { resourceType: "llm_model", projectId } If none: run setup_llm
- Check agent description is not empty: get_resource { resourceType: "agent", id }
- Check endpoint is connected: get_resource { resourceType: "endpoint", id } Verify flowId is set and URLToken exists
- Endpoint JUST created (seconds ago)? Endpoint config propagates briefly, and a session whose FIRST message hit the stale config stays cached as broken — wait a few seconds and retry with a NEW sessionId, not the same one.
- LLM Prompt flows: the assigned LLM must have a connection (
connectionIdset on the llm_model). A connectionless LLM fails silently — the node's default error handling is "continue" with an empty message, which looks like an empty response.
talk_to_agent fails (any HTTP error or timeout)
talk_to_agent sends through Cognigy Endpoint Test Mode (/test/<token>) so test
messages are not counted as billable. It never re-sends a failed message on the regular
(billable) endpoint by itself; a failure comes back as error with testMode,
endpointUrl and status-aware _hints.
Step 1, always: find out whether the message was processed. An HTTP error
does not prove it was not. A REST endpoint's Execution Finished transformer runs
after the flow and can return any status (a 404 included), and a gateway timeout
can hide a completed execution. Waiting or reusing the sessionId does not
prevent a duplicate. Check:
get_resource { resourceType: "conversation", id: "<sessionId>" }for the transcript (needs the endpoint to collect conversations), or- continue the same
sessionIdwith a neutral follow-up ("what did you just do?"), or verify the side effects of the agent's tools.
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.
- 14d ago Changed · +10 lines 0c0e4bc958be
- 1mo ago Changed · +6 lines 232fc4cfd50f
- 1mo ago Changed · +47 lines 15a352bf3cdc
- 1mo ago Changed · +6 lines 9e586558ffbe
- 1mo ago Changed · +23 lines d3ab6ddfcd7b
- 2mo ago First seen · 55 lines · 45 tokens per session scan A b5a10ef3595c
troubleshooting is a skill published in the GitHub repository Cognigy/cognigy-plugin (18 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 2,168 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.
troubleshooting compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| troubleshootingCognigy/cognigy-plugin | Skill | 18 | yesterday | MIT | A | 45 | Claude Code |
| systematic-debuggingopen-metadata/OpenMetadata | Skill | 16k | yesterday | Apache-2.0 | A | 37 | Claude Code |
| log-error-digestzebbern/claude-code-guide | Skill | 4.7k | 3d ago | MIT | A | 71 | Claude Code, Codex |
| cwv-optimizeradobe/skills | Skill | 319 | yesterday | Apache-2.0 | A | 112 | Claude Code |
| ci-fixersipyourdrink-ltd/bernstein | Skill | 1.2k | yesterday | Apache-2.0 | A | 15 | Claude Code, Codex |
| incident-response-incident-responsermyndharis/antigravity-skills | Skill | 1.9k | 23d ago | MIT | A | 36 | Claude Code |
| triaging-web-analytics-supportPostHog/posthog | Skill | 41k | yesterday | none | A | 151 | Claude Code, Codex |