OpenTag is a self-hosted AI agent that handles knowledge-work requests inside Slack and Microsoft Teams, using connected tools and generated interfaces. Teams can use it as an on-call triage bot or customize it for their own agent workflows. Its catalogue add-ons support the agent, tools, and integrations assembled in the starter application.
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 CopilotKit/OpenTag --skill implement-issuegit clone --depth 1 https://github.com/CopilotKit/OpenTagWrote 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/copilotkit/opentag/implement-issue)<a href="https://agentmods.dev/skills/copilotkit/opentag/implement-issue"><img src="https://agentmods.dev/badge/skills/copilotkit/opentag/implement-issue/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/copilotkit/opentag/implement-issue"><img src="https://agentmods.dev/badge/skills/copilotkit/opentag/implement-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00035 | $0.00230 |
| Opus 5.5 | $0.00014 | $0.00092 |
| Sonnet 5.5 | $0.00007 | $0.00046 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
implement-issue 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.
What it actually says
implement-issue
Implement only the brief. Do not rediscover the issue. Do not explore the repo to invent a plan.
The brief must include repo, issue, files, change, and one
test command. If any of those are missing, stop. Return
status: failed and say the brief is incomplete. Do not guess.
- Call
prepare_repositorywith the repo and branchopentag/<issue-id>. - Work from the returned directory and branch.
- Edit only the listed files.
- Run the one test command from the brief.
- Do not guess
pnpm test. Do not run the full monorepo suite. - If green, commit locally and call
publish_changes. - If red, do not call
publish_changesunless the brief saysopen_anyway: true.
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 · 24 lines · 35 tokens per session scan A 7c70012f5c62
implement-issue is a skill published in the GitHub repository CopilotKit/OpenTag (1,267 stars, last pushed 3d ago), licensed MIT. It adds 35 tokens to every session and 230 once invoked, about $0.0001 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-30.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
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)…
cuga-github-issues
Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking. Use when the user says create new issues, report a bug, file a bug, feature request, new feature, create an epic, GitHub issue, sub-issue…
dot-ai-projectSetup
Setup project, audit repository, or generate repository files. Use this when user wants to: setup project, audit repo, check missing files, create README, add LICENSE, generate CONTRIBUTING.md, add CI/CD workflows, initialize documentation, setup governance files. Analyzes local repositories and generates missing…