Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add cogni-work/insight-wave/plugin install cogni-workspaceWrote 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/cogni-work/insight-wave/cogni-issues)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/cogni-issues"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/cogni-issues/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/cogni-work/insight-wave/cogni-issues"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/cogni-issues.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.00160 | $0.04472 |
| Opus 5.5 | $0.00064 | $0.01789 |
| Sonnet 5.5 | $0.00032 | $0.00894 |
| Haiku 4.5 | $0.00016 | $0.00447 |
Grade A, and why
cogni-issues 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 1mo 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 — 434 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cogni Issues
Manage the lifecycle of GitHub issues for insight-wave ecosystem plugins: consult with the
user to understand the problem clearly, resolve which repository the plugin belongs to,
draft issues from templates, create them via gh issue create, and track them locally.
All GitHub operations use the gh CLI — atomic, scriptable, and the same transport
the rest of the cogni-service pipeline uses. The user must have gh installed and
authenticated (gh auth login) before this skill runs.
The reliability win over a browser-automation transport is concrete: labels are applied in the same API call that creates the issue (no "best-effort fallback" that silently drops type signals), the flow runs equally well from a remote routine, and the skill has no MCP-server dependency.
Language
Read the workspace language from .workspace-config.json in the workspace root
(language field — "en" or "de") as the default interaction language. If the
user's message is in a different language, prefer the user's language (message
detection overrides the workspace setting — someone writing in German wants a
German response even if the workspace is set to English).
If .workspace-config.json is missing, fall back to detecting the user's language
from their message. If still unclear, default to English.
Conduct the entire interaction in the chosen language — consultation questions, acknowledgments, draft body, and confirmation prompts.
Exceptions where English stays:
- Title prefixes:
[Bug],[Feature],[Change],[Question]— conventions for GitHub label automation and cross-team readability. - Technical terms: plugin names, CLI commands, error messages, stack traces.
Environment
The skill scripts live at ${CLAUDE_PLUGIN_ROOT}/skills/cogni-issues/scripts/.
CLAUDE_PLUGIN_ROOT points to the cogni-workspace plugin directory. If the scripts
cannot be found, report the missing path to the user — never guess paths.
gh CLI commands
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 434 lines · 160 tokens per session scan A c2ca2f5e4ade
cogni-issues is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 160 tokens to every session and 4,472 once invoked, about $0.0006 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-09-14.
Other skills, from other repositories
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…