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/hasithaishere/buildkite-developer-toolkit/buildkite-mcp-debuggingnpx skills add hasithaishere/buildkite-developer-toolkit --skill buildkite-mcp-debugginggit clone --depth 1 https://github.com/hasithaishere/buildkite-developer-toolkitWrote 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/hasithaishere/buildkite-developer-toolkit/buildkite-mcp-debugging)<a href="https://agentmods.dev/skills/hasithaishere/buildkite-developer-toolkit/buildkite-mcp-debugging"><img src="https://agentmods.dev/badge/skills/hasithaishere/buildkite-developer-toolkit/buildkite-mcp-debugging.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 | $0.00096 | $0.01033 |
| Opus 5 | $0.00048 | $0.00517 |
| Sonnet 5 | $0.00019 | $0.00207 |
| Haiku 4.5 | $0.00010 | $0.00103 |
Grade A, and why
buildkite-mcp-debugging 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 4d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Buildkite live debugging & real-time accuracy
This skill does two things: inspect real builds via the Buildkite MCP server, and keep answers accurate by checking the live documentation.
References (verify here):
- MCP overview: https://buildkite.com/docs/apis/mcp-server
- Configure AI tools: https://buildkite.com/docs/apis/mcp-server/remote/configuring-ai-tools
- Toolsets: https://buildkite.com/docs/apis/mcp-server/tools/toolsets
A. Debugging with the Buildkite MCP server
The MCP server exposes Buildkite read/write operations as tools. It is not bundled in this plugin (so you never ship credentials); the user adds it once.
One-time setup (user runs this)
# Full access:
claude mcp add --transport http buildkite https://mcp.buildkite.com/mcp
# Read-only (recommended for debugging — can't mutate anything):
claude mcp add --transport http buildkite-ro https://mcp.buildkite.com/mcp/readonly \
--header "X-Buildkite-Toolsets: user,pipelines,builds,agents"
The remote server authenticates via Buildkite's OAuth flow on first use. See the README "Connecting the Buildkite MCP server" section.
Using it
Once connected, MCP tools appear (typically prefixed mcp__buildkite__*). If
you don't see them, use ToolSearch to load them. Toolsets group the tools:
user— who am I / which org (validate the token first).pipelines— list/get pipelines (and create/update with write access).builds— list/get builds, get a build's jobs, fetch logs, wait for builds.agents— which agents are connected and their state.
Debugging workflow
- Confirm access: call the
user/token tool to verify org + scope. - Locate the build: list builds for the pipeline (filter by branch/state), or get a specific build by number.
- Find the failing job/step: get the build's jobs; identify the non-zero / failed one and which hook or command it was.
- Read the log: fetch that job's log. Look for: the failing command, the
last hook that ran,
set -eaborts, missing env vars, and any+++/^^^Buildkite log group markers near the failure. - Correlate to code: map the failure to the pipeline step or plugin hook.
For plugin issues, hand off to
buildkite-plugin-dev; for pipeline structure, topipeline-architecture(and validate fixes with--dry-run). - Propose a fix and, if the user wants, re-run via the MCP write 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.
- 4d ago First seen · 87 lines · 96 tokens per session scan A 17059dd22296
buildkite-mcp-debugging is a skill published in the GitHub repository hasithaishere/buildkite-developer-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 96 tokens to every session and 1,033 once invoked, about $0.0005 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…