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/pipeline-securitynpx skills add hasithaishere/buildkite-developer-toolkit --skill pipeline-securitygit 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/pipeline-security)<a href="https://agentmods.dev/skills/hasithaishere/buildkite-developer-toolkit/pipeline-security"><img src="https://agentmods.dev/badge/skills/hasithaishere/buildkite-developer-toolkit/pipeline-security.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.00135 | $0.01442 |
| Opus 5 | $0.00068 | $0.00721 |
| Sonnet 5 | $0.00027 | $0.00288 |
| Haiku 4.5 | $0.00014 | $0.00144 |
Grade A, and why
pipeline-security scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`privileged`, `propagate-environment`, build-metadata injection, `curl|bash`) How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Buildkite pipeline & CI/CD security review
You are a security engineer auditing a Buildkite pipeline and its agents. The guiding rule: secrets never live in YAML or logs, code from untrusted sources never reaches secrets or privileged infrastructure, and the agent enforces what it will run.
Verify specifics against the docs:
- Securing the agent: https://buildkite.com/docs/agent/v3/securing
- Enforcing security controls: https://buildkite.com/docs/pipelines/best-practices/security-controls
- Signed pipelines: https://buildkite.com/docs/agent/v3/signed-pipelines
- Agent hooks: https://buildkite.com/docs/agent/hooks
- OIDC: https://buildkite.com/docs/pipelines/security/oidc
Threat model
- Pipeline YAML and
pipeline uploadcan come from untrusted contributors (fork/PR builds). Assume an attacker can propose steps, commands, env, and plugin refs. - Agents are shared, privileged infrastructure — they hold (or can mint) secrets and can reach your cloud/registries and other jobs' state.
- Plugins and the pipeline are a supply chain — a moved tag or smuggled step is RCE on your agents.
How to run the scan
bash "${CLAUDE_SKILL_DIR}/scripts/scan-pipeline.sh" <repo-or-pipeline-path>
Static checks (unpinned/mutable plugins, inline secrets, Docker socket,
privileged, propagate-environment, build-metadata injection, curl|bash)
plus gitleaks when installed. Exits non-zero on any HIGH (--no-fail to
report-only). Wire it into CI. Full catalog: reference/vulnerability-catalog.md.
1. Secrets
- Never in
pipeline.yml, stepenv:, orcommandstrings; neverechoed. - Prefer OIDC (short-lived, keyless) over static credentials; bind the cloud trust policy to specific claims (org / pipeline slug / branch).
- Otherwise fetch at runtime from a managed store (AWS/GCP Secrets Manager,
Vault) or the Buildkite secrets feature, in an
environment/pre-commandhook, scoped to where needed. Rely on agent redaction as a backstop, not a primary control.
What ships with it
6 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.
- 4d ago First seen · 111 lines · 135 tokens per session scan A fb8b3ba037ae
pipeline-security is a skill published in the GitHub repository hasithaishere/buildkite-developer-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 135 tokens to every session and 1,442 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
tinybird-cli-guidelines
Tinybird CLI commands, workflows, and operations. Use when running tb commands, managing local development, deploying, or working with data operations.
ci-security-scanning-with-strix
Add security scanning to CI/CD with Strix — GitHub Actions, GitLab CI, or any pipeline — so every pull request gets a diff-scoped AI pentest that blocks vulnerable code before it merges, with results as PR comments and SARIF uploaded to code scanning. Covers both the self-hosted open-source CLI (runs in your runner)…
desktop-principles
Desktop-specific UX principles - hover states, pointer precision, keyboard shortcuts, multi-window, focus management. Covers macOS, Windows, Linux, web desktop.
upgrading-golang
Upgrades Go version across the entire Chainloop codebase including source files, Docker images, CI/CD workflows, and documentation. Use when the user mentions upgrading Go, golang version, or updating Go compiler version.
python-canary-fix
Investigate and propose fixes for Python canary cron failures in the openinference repo. Use when the user mentions Python canary failures, Python cron failures, or when the auto-fix CI job reports Python instrumentation canary issues.
ci-fixer
CI failures - read error, minimal fix, verify.