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 selvarajmurugesan90/ops-engineering-skills --skill bamboo-pipeline-yaml-and-java-specsgit clone --depth 1 https://github.com/selvarajmurugesan90/ops-engineering-skillsWrote 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/selvarajmurugesan90/ops-engineering-skills/bamboo-pipeline-yaml-and-java-specs)<a href="https://agentmods.dev/skills/selvarajmurugesan90/ops-engineering-skills/bamboo-pipeline-yaml-and-java-specs"><img src="https://agentmods.dev/badge/skills/selvarajmurugesan90/ops-engineering-skills/bamboo-pipeline-yaml-and-java-specs/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/selvarajmurugesan90/ops-engineering-skills/bamboo-pipeline-yaml-and-java-specs"><img src="https://agentmods.dev/badge/skills/selvarajmurugesan90/ops-engineering-skills/bamboo-pipeline-yaml-and-java-specs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 216 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 228 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 326 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 331 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 333 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00114 | $0.03328 |
| Opus 5 | $0.00057 | $0.01664 |
| Sonnet 5 | $0.00023 | $0.00666 |
| Haiku 4.5 | $0.00011 | $0.00333 |
Grade A, and why
bamboo-pipeline-yaml-and-java-specs 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 11d 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 — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bamboo Pipeline YAML and Java Specs
Purpose
Atlassian Bamboo predates most "pipeline as code" conventions and historically configured plans through its web UI. Bamboo Specs bring plans under version control two ways: a Java DSL (compiled and run as a small program that calls the Bamboo REST API to create/update a plan) or Bamboo's newer YAML specs format (a declarative file read directly from the repo, closer to GitHub Actions/GitLab CI in spirit). This skill covers both, plus Bamboo's plan → job → stage → task hierarchy (distinct from GitHub Actions' workflow → job → step or GitLab's stage → job model) and the mechanics of linking a Specs definition to a live Bamboo plan so changes actually take effect.
When to use
- A team currently configures Bamboo plans by hand through the UI and wants them version-controlled and code-reviewed instead.
- Writing or debugging a Bamboo Specs Java class that isn't correctly creating/updating the target plan.
- Choosing between the Java DSL and YAML specs format for a new Bamboo project.
- A plan/job/stage structure needs redesigning (e.g. splitting a monolithic job into parallel jobs within a stage).
- Migrating from a UI-configured Bamboo plan to a Specs-managed one without losing build history or breaking existing triggers.
Prerequisites & environment
- A Bamboo Server or Data Center instance (Bamboo Specs and YAML specs
both require Bamboo 6.x+; check the specific Bamboo version's
documentation for exact Java Specs library compatibility, since
Atlassian versions the
atlassian-bamboo-specsartifact alongside Bamboo server releases and mismatches cause API-shape errors). - For Java Specs: a JVM (Java 11+ typically) and Maven/Gradle to compile
and run the Specs program; the
atlassian-bamboo-specsdependency matching the target Bamboo server's version. - For YAML specs: Bamboo Data Center with YAML specs enabled for the
project, and a
bamboo-specs/(or configured path) directory in the repo containing the.yamlfiles. - A Bamboo user/service account with permission to create/edit plans in the target project, and its credentials configured wherever the Specs runner executes (CI job, or a "Bamboo Specs" repository trigger).
- An existing Bamboo project to house the plan (Specs create/update plans within a project; they don't create a project from scratch by default).
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.
- 11d ago First seen · 334 lines · 114 tokens per session scan A f86d95024895
bamboo-pipeline-yaml-and-java-specs is a skill published in the GitHub repository selvarajmurugesan90/ops-engineering-skills (38 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 114 tokens to every session and 3,328 once invoked, about $0.0006 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-30.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.