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/asleekgeek/claude-multiagent-catalogueWrote 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/agents/asleekgeek/claude-multiagent-catalogue/atlassian-requirements-to-jira)<a href="https://agentmods.dev/agents/asleekgeek/claude-multiagent-catalogue/atlassian-requirements-to-jira"><img src="https://agentmods.dev/badge/agents/asleekgeek/claude-multiagent-catalogue/atlassian-requirements-to-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/agents/asleekgeek/claude-multiagent-catalogue/atlassian-requirements-to-jira"><img src="https://agentmods.dev/badge/agents/asleekgeek/claude-multiagent-catalogue/atlassian-requirements-to-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.00035 | $0.04006 |
| Opus 5.5 | $0.00014 | $0.01602 |
| Sonnet 5.5 | $0.00007 | $0.00801 |
| Haiku 4.5 | $0.00003 | $0.00401 |
Grade A, and why
atlassian-requirements-to-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 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 450 lines · 35 tokens per session scan A 34e562797f4a
atlassian-requirements-to-jira is an agent published in the GitHub repository asleekgeek/claude-multiagent-catalogue (2 stars, last pushed 5mo ago), with no licence file. It adds 35 tokens to every session and 4,006 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 agents, from other repositories
scrum-master
Shards the approved plan into small, independently testable stories under docs/stories/. Use once the owner has approved the plan.
product-strategist
Turns ideas and problems into clear product decisions. Use for scoping features, writing specs, prioritization, and pressure-testing what to build and why.
plan-auditor
Audits planning artifacts in two modes. Gate mode checks that requirements, design, and stories are aligned before implementation starts and returns READY, NEEDS WORK, or NOT READY. Change-impact mode traces a requirement change, blocker, or scope shift across the plan and drafts a change proposal. Delegate when…
parallel-integrate
Integrate parallel workflow branches. Use after all workers complete to merge branches, resolve conflicts, finalize integration. Triggers: integrate, merge workers, combine branches, finish parallel.
talent-scout
Use this agent for continuous team-coverage gap detection and structured hiring-requisition drafting — it senses when the user's active work is drifting into a domain the team does not specialize in, composes a 5-signal weighted confidence score, and (only with session-sentinel co-sign at ≥90% confidence) drafts a…
drupal-tech-lead
Use this agent when you need expert Drupal technical leadership for architecture decisions, team coordination, and project governance. Examples: designing complex Drupal multisite architectures, establishing coding standards and review processes, creating technical specifications for modules and integrations…