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 jira-syntaxgit 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/jira-syntax)<a href="https://agentmods.dev/skills/sergeyklay/.agents/jira-syntax"><img src="https://agentmods.dev/badge/skills/sergeyklay/.agents/jira-syntax/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/jira-syntax"><img src="https://agentmods.dev/badge/skills/sergeyklay/.agents/jira-syntax.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.00082 | $0.01462 |
| Opus 5 | $0.00041 | $0.00731 |
| Sonnet 5 | $0.00016 | $0.00292 |
| Haiku 4.5 | $0.00008 | $0.00146 |
Grade A, and why
jira-syntax 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 9d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira wiki markup
Jira uses its own wiki notation that differs from Markdown in every formatting construct. Agents default to Markdown. Mixing the two produces broken rendering in Jira. This skill ensures correct output.
Running scripts bundled with this skill
Script paths in this document (e.g. scripts/) are resolved relative to this SKILL.md file, not to your current working directory. If a relative command fails to resolve, prefix it with the path your platform loaded this SKILL.md from.
Fallback. If python3 cannot be located, analyze the script's purpose and logic and execute its intent with available tools, but warn the user that python is not available and the logic was executed with a fallback approach that may not be perfect.
Markdown-to-Jira conversion table
These substitutions are mandatory when targeting Jira:
| Concept | Jira wiki markup | NOT Markdown |
|---|---|---|
| Heading | h2. Title |
## Title |
| Bold | *bold* |
**bold** |
| Italic | _italic_ |
*italic* |
| Inline code | {{code}} |
`code` |
| Code block | {code:java}...{code} |
```java ``` |
| Link | [text|url] |
[text](url) |
| Issue link | [PROJ-123] |
n/a |
| User mention | [~username] |
@username |
| Bullet list | * item |
- item |
| Numbered list | # item |
1. item |
| Table header | ||Header|| |
|Header| |
Read references/syntax-reference.md for the complete notation including panels, colors, nested lists, and special blocks.
Conversion examples
Example 1 (bug comment with code):
Input (Markdown):
## Root cause
The `processData()` function throws when **input is null**.
- Missing null check on line 45
- Related: see issue #123
Output (Jira wiki markup):
h2. Root cause
The {{processData()}} function throws when *input is null*.
* Missing null check on line 45
* Related: see [PROJ-123]
Example 2 (status update with table):
Input (Markdown):
### Sprint progress
| Task | Status | Owner |
|------|--------|-------|
| Auth module | Done | @john |
| API docs | In progress | @jane |
What ships with it
4 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.
- 9d ago First seen · 135 lines · 82 tokens per session scan A 5b4707f54f27
jira-syntax is a skill published in the GitHub repository sergeyklay/.agents (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 82 tokens to every session and 1,462 once invoked, about $0.0004 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
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.
agentrq
Lead multiple agents to accomplish big tasks with specialized workspaces/agents by assigning tasks to specialized agents.
work
Execute Elixir/Phoenix plan tasks with progress tracking. Use after /phx:plan to implement features with mix compile and mix test verification after each step, or --continue to resume interrupted work.
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
plan
Plan features spanning multiple domains: billing (Stripe), auth (RBAC), real-time (Presence), webhooks, jobs (Oban). Use when designing interconnected systems or converting review findings into tasks.
phx-deps-update
Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (phx-investigate).