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 cloudbees-oss/devops-agent-kit --skill file-ticketgit clone --depth 1 https://github.com/cloudbees-oss/devops-agent-kitWrote 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/cloudbees-oss/devops-agent-kit/file-ticket)<a href="https://agentmods.dev/skills/cloudbees-oss/devops-agent-kit/file-ticket"><img src="https://agentmods.dev/badge/skills/cloudbees-oss/devops-agent-kit/file-ticket/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/cloudbees-oss/devops-agent-kit/file-ticket"><img src="https://agentmods.dev/badge/skills/cloudbees-oss/devops-agent-kit/file-ticket.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.00019 | $0.00374 |
| Opus 5.5 | $0.00008 | $0.00150 |
| Sonnet 5.5 | $0.00004 | $0.00075 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
file-ticket 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
File Jira Ticket
Parse arguments to determine issue type and description.
-
If the agent has recent triage/scan context, use it. Otherwise, ask which component and issue to reference.
-
Build the Jira ticket:
For build failures:
- Summary: "[Build Failure] {component} — {root_cause_summary}"
- Description: Root cause analysis, failing step, log excerpt (if available), fix recommendation, link to run
- Labels: build-failure, devops-agent
- Priority: High if blocking all builds, Medium if intermittent
For security findings:
- Summary: "[Security] {component} — {finding_type} in {file_path}"
- Description: Finding details (severity, scanner, file, line), SLA due date, remediation steps, affected environments
- Labels: security, devops-agent
- Priority: based on severity (Critical/High = High, Medium = Medium, Low = Low)
For improvements:
- Summary: "[Improvement] {description}"
- Description: Current state, proposed change, expected impact, implementation steps
- Labels: improvement, devops-agent
- Priority: Medium (default)
-
Show the ticket preview and ask for confirmation
-
Create via
mcp__mcp-atlassian__jira_create_issue -
Confirm with ticket URL
-
Offer to:
- Post the ticket link to Slack
- Add the ticket as a GitHub issue comment on the relevant PR
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 · 45 lines · 19 tokens per session scan A aab8a94609e6
file-ticket is a skill published in the GitHub repository cloudbees-oss/devops-agent-kit (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 374 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-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…