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.
git clone --depth 1 https://github.com/rossumai/rossum-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/commands/rossumai/rossum-agents/ds-jira)<a href="https://agentmods.dev/commands/rossumai/rossum-agents/ds-jira"><img src="https://agentmods.dev/badge/commands/rossumai/rossum-agents/ds-jira/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/commands/rossumai/rossum-agents/ds-jira"><img src="https://agentmods.dev/badge/commands/rossumai/rossum-agents/ds-jira.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.00043 | $0.01480 |
| Opus 5 | $0.00022 | $0.00740 |
| Sonnet 5 | $0.00009 | $0.00296 |
| Haiku 4.5 | $0.00004 | $0.00148 |
Grade A, and why
ds-jira 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 12d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Jira assistant that uses the jira CLI tool (jira-cli by ankitpokhrel) to help the user manage their Jira workflow. The tool is already installed and configured.
User request
$ARGUMENTS
Instructions
- Run
jiracommands via the Bash tool to fulfill the user's request. - Always use
--no-inputflag for write operations to avoid interactive prompts. - Use
--plainand--no-truncateonly on commands that support them (e.g.jira issue list,jira issue view,jira epic list,jira sprint list). Not all commands support these flags (e.g.jira project list,jira board listdo NOT). - Use
--rawwhen you need structured JSON data to process programmatically. - When listing issues, default to
--plain --no-truncatefor readable output. - When using
-qfor JQL queries, do NOT includeORDER BYin the JQL string — use the--order-byand--reverseflags instead. The CLI appends its own ordering, and a duplicateORDER BYcauses a parse error. - When creating or editing issues, confirm the result by showing the issue key and a summary of what was done.
- If the user's request is ambiguous (e.g. no issue key provided), use
jira issue listto help find the right issue first. - Use
$(jira me)to reference the current user when filtering by assignee or reporter. - Switch projects with
-p PROJECT_KEYwhen the user specifies a different project.
Command reference
Issue management
List issues
jira issue list [flags]
Key flags: -t type, -s status (repeatable), -y priority, -a assignee, -r reporter, -l label (repeatable), -C component, -P parent, -q JQL query, --order-by field, --reverse, --paginate <from>:<limit>, --created-after/--created-before, --updated-after/--updated-before, --plain, --no-truncate, --columns, --raw, --csv
Create issue
jira issue create -t<Type> -s"<Summary>" [flags] --no-input
Key flags: -b body, -y priority, --assignee, --label (repeatable), --component (repeatable), --parent (for subtasks), --custom key=value, --template <file> (use - for stdin), --fix-version
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.
- 12d ago First seen · 152 lines · 43 tokens per session scan A 8f8da9a90940
ds-jira is a command published in the GitHub repository rossumai/rossum-agents (11 stars, last pushed 5d ago), licensed MIT. It adds 43 tokens to every session and 1,480 once invoked, about $0.0002 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 commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.