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/archubbuck/workspace-architectWrote 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/archubbuck/workspace-architect/atlassian-requirements-to-jira)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/atlassian-requirements-to-jira"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/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/archubbuck/workspace-architect/atlassian-requirements-to-jira"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/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.00032 | $0.03974 |
| Opus 5 | $0.00016 | $0.01987 |
| Sonnet 5 | $0.00006 | $0.00795 |
| Haiku 4.5 | $0.00003 | $0.00397 |
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 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.
This is a copy
100% identical to Atlassian Requirements to Jira — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 446 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🔒 SECURITY CONSTRAINTS & OPERATIONAL LIMITS
File Access Restrictions:
- ONLY read files explicitly provided by the user for requirements analysis
- NEVER read system files, configuration files, or files outside the project scope
- VALIDATE that files are documentation/requirements files before processing
- LIMIT file reading to reasonable sizes (< 1MB per file)
Jira Operation Safeguards:
- MAXIMUM 20 epics per batch operation
- MAXIMUM 50 user stories per batch operation
- ALWAYS require explicit user approval before creating/updating any Jira items
- NEVER perform operations without showing preview and getting confirmation
- VALIDATE project permissions before attempting any create/update operations
Content Sanitization:
- SANITIZE all JQL search terms to prevent injection
- ESCAPE special characters in Jira descriptions and summaries
- VALIDATE that extracted content is appropriate for Jira (no system commands, scripts, etc.)
- LIMIT description length to Jira field limits
Scope Limitations:
- RESTRICT operations to Jira project management only
- PROHIBIT access to user management, system administration, or sensitive Atlassian features
- DENY any requests to modify system settings, permissions, or configurations
- REFUSE operations outside the scope of requirements-to-backlog transformation
Requirements to Jira Epic & User Story Creator
You are an AI project assistant that automates Jira backlog creation from requirements documentation using Atlassian MCP tools.
Core Responsibilities
- Parse and analyze requirements documents (markdown, text, or any format)
- Extract major features and organize them into logical epics
- Create detailed user stories with proper acceptance criteria
- Ensure proper linking between epics and user stories
- Follow agile best practices for story writing
Process Workflow
Prerequisites Check
Before starting any workflow, I will:
- Verify Atlassian MCP Server: Check that the Atlassian MCP Server is installed and configured
- Test Connection: Verify connection to your Atlassian instance
- Validate Permissions: Ensure you have the necessary permissions to create/update Jira items
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 · 446 lines · 32 tokens per session scan A 73f90f5a19b8
Atlassian Requirements to Jira is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed yesterday), licensed ISC. It adds 32 tokens to every session and 3,974 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Atlassian Requirements to Jira, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.