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 sergeyklay/.agents --skill manage-ticketsgit clone --depth 1 https://github.com/sergeyklay/.agentsWrote 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/sergeyklay/.agents/manage-tickets)<a href="https://agentmods.dev/skills/sergeyklay/.agents/manage-tickets"><img src="https://agentmods.dev/badge/skills/sergeyklay/.agents/manage-tickets/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/sergeyklay/.agents/manage-tickets"><img src="https://agentmods.dev/badge/skills/sergeyklay/.agents/manage-tickets.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 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 Prompt Injection · line 41 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 66 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 70 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Excessive Agency · line 246 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00238 | $0.04017 |
| Opus 5.5 | $0.00095 | $0.01607 |
| Sonnet 5.5 | $0.00048 | $0.00803 |
| Haiku 4.5 | $0.00024 | $0.00402 |
Grade A, and why
manage-tickets 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 14d 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.
1. Atlassian MCP server is available. MCP is the only path to Jira - never `curl`, never bare HTTP, never `gh`. How it starts
The opening of the file, as written. The whole thing — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Managing Jira Tickets
Manage Jira tickets via the Atlassian MCP. Every ticket must be self-contained, professional, and actionable without prior context. The skill applies only to Jira sites the Atlassian MCP is connected to; if the MCP is unavailable, stop and tell the user.
Prerequisites
- Atlassian MCP server is available. MCP is the only path to Jira - never
curl, never bare HTTP, nevergh. jira-syntaxskill is loaded before composing any field content. Jira description and comment fields are wiki markup, not Markdown.
Discover project metadata (run first)
Before any create, edit, search, or transition operation, fetch the live metadata for the target site and project:
| Need | Tool |
|---|---|
Jira site cloudId |
getAccessibleAtlassianResources |
| Visible projects and their keys | getVisibleJiraProjects |
| Types accepted by chosen project | getJiraProjectIssueTypesMetadata |
| Required fields for a chosen type | getJiraIssueTypeMetaWithFields |
| Site-wide issue link types | getIssueLinkTypes |
| Valid transitions for an issue | getTransitionsForJiraIssue |
| Resolve display name to account id | lookupJiraAccountId |
Use the values verbatim. Never memorize project keys, type names, transition IDs, label names, or account IDs across sessions.
What to do when discovery returns nothing, returns several projects, lacks the type you classified, or reports required custom fields is tabulated in references/ticket-operations.md § Discovery branching.
Body shape
Tickets share three common sections; the middle is type-specific.
| Section | Position | Purpose |
|---|---|---|
| Summary | Top | One paragraph stating what the ticket addresses. Not a restatement of the title. |
| (type-specific) | Middle | Background, observed behaviour, root cause, proposed solution, scope, etc. - varies per type. |
| Requirements | Near end | Observable outcomes in MUST / MUST NOT form. Each independently verifiable. |
| [Self-checks] | Optional | Automated (CI assertions) and Manual (operator-runnable scenarios). Encouraged for Bug, Story, Task. |
| Context | Bottom | Origin (where the ticket came from), verbatim operator/reviewer quote, related tickets, tracking links. |
What ships with it
8 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.
- 14d ago Changed 365f7bde8e49
- 1mo ago Changed · +1 lines b8e1a52a210e
- 1mo ago Changed · +42 tokens per session f8dcd201fa83
- 1mo ago Changed · +3 lines 4ab5138be296
- 1mo ago Changed · -29 lines 995f4edc86e9
- 1mo ago First seen · 282 lines · 196 tokens per session scan A 1e3a87f34a13
manage-tickets is a skill published in the GitHub repository sergeyklay/.agents (6 stars, last pushed 6d ago), licensed Apache-2.0. It adds 238 tokens to every session and 4,017 once invoked, about $0.0010 per session on Opus 5.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
glab-gitlab-issue
Read and manage GitLab issues through the glab CLI. Use when a user provides an issue ID and repository and asks to view issue details, comments, or uploaded images, publish comments, update assignees or labels, or manage issue time tracking (estimate/spent time) without using the web UI.
procurement-optimizer
Use when running an annual SaaS audit, doing category-level spend review, or rationalizing the supplier base — when the user needs a spend audit, spend categorization (UNSPSC-aligned with Pareto breakdown and industry profiles), purchasing-cycle analysis (bottleneck categories per Goldratt's Theory of Constraints), or…
capacity-planner
Use when an ops leader (Director of CX, Head of Support, VP Ops, Head of BizOps, Head of IT ops, Head of Finance ops) is sizing ops capacity, building a headcount plan, modeling utilization risk, planning Q3 capacity or annual support capacity, or designing CS coverage — and needs Erlang-C queueing math, P90 demand…
chief-customer-officer-advisor
Chief Customer Officer advisory for startups: retention decomposition (gross retention vs NRR honesty, churn root-cause taxonomy), customer segmentation strategy (differential investment across tiers + ICP fit scoring), CS team coverage model (pooled vs named CSM thresholds + ratio math), and CS team org evolution (CS…
business-operations-skills
Use when running, diagnosing, or designing internal business operations — process documentation, vendor SLAs, capacity planning, internal comms, SOP/runbook authoring, procurement spend. Triggers on "BizOps review", "where's the bottleneck", "vendor health", "internal SOP", "all-hands deck", "spend categorization"…
cpo-advisor
Product leadership for scaling companies. Product vision, portfolio strategy, product-market fit, and product org design. Use when setting product vision, managing a product portfolio, measuring PMF, designing product teams, prioritizing at the portfolio level, reporting to the board on product, or when user mentions…