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 open-metadata/ai-sdk --skill debug-cigit clone --depth 1 https://github.com/open-metadata/ai-sdkWrote 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/open-metadata/ai-sdk/debug-ci)<a href="https://agentmods.dev/skills/open-metadata/ai-sdk/debug-ci"><img src="https://agentmods.dev/badge/skills/open-metadata/ai-sdk/debug-ci/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/open-metadata/ai-sdk/debug-ci"><img src="https://agentmods.dev/badge/skills/open-metadata/ai-sdk/debug-ci.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.00040 | $0.00797 |
| Opus 5.5 | $0.00016 | $0.00319 |
| Sonnet 5.5 | $0.00008 | $0.00159 |
| Haiku 4.5 | $0.00004 | $0.00080 |
Grade A, and why
debug-ci 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 120 lines · 40 tokens per session scan A f4a20679eb43
debug-ci is a skill published in the GitHub repository open-metadata/ai-sdk (15 stars, last pushed 7d ago), with no licence file. It adds 40 tokens to every session and 797 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-30.
Other skills, from other repositories
lsp-mcp-server
Use with Codex, Claude Code, or another MCP client when lsp-mcp-server is connected and semantic code navigation, analysis, refactoring, or diagnostics are needed. Covers all 29 lsp tools for TypeScript, Python, Rust, Go, C/C++, Ruby, PHP, Elixir, Kotlin, Java, and user-configured languages. Prefer these tools to text…
lain
Structural code intelligence for AI coding agents. Use this skill when the user wants to understand how a codebase is organized (modules, call graphs, file dependencies), find where to start reading, trace the impact of a change, find code by meaning, or understand what a symbol does in its full context. Do NOT use…
explore
Build an accurate mental model of an unfamiliar codebase, feature, or area before changing it — where it lives, how it connects, what it does, and why. Use when asked how something works, where something is, when onboarding to a repo, or before editing code you don't know. For a cross-cutting question that needs…
debug
Trace a bug, error, or regression to its root cause. Use when investigating a failure, a stack trace, unexpected behavior, or "why does X happen".
lain-architecture
Use for system-shape questions through Lain — "map this subsystem", "compare these modules", "trace the dependency chain", "how deep is this in the stack", "where is the god object", "run a raw graph query". Covers the arch and raw packages.
lain-comprehension
Use when reading, locating, or assessing code through Lain's MCP tools — "where is X", "explain this", "what breaks if I change this", "what should I read first", "is this answer trustworthy". Covers the default core surface and the honest-answer contract.