Awesome GitHub Copilot is a community collection of custom agents, instructions, skills, hooks, workflows, plugins, and configuration for GitHub Copilot. It helps Copilot users customize coding and development tasks. Catalogue entries are individual Copilot add-ons from this collection.
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/github/awesome-copilotWrote 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/github/awesome-copilot/atlassian-requirements-to-jira)<a href="https://agentmods.dev/agents/github/awesome-copilot/atlassian-requirements-to-jira"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/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/github/awesome-copilot/atlassian-requirements-to-jira"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/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.5 | $0.00013 | $0.01590 |
| Sonnet 5.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 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- Atlassian Requirements to Jira — 100% identical, 0 lines differ
- Atlassian Requirements to Jira — 100% identical, 0 lines differ
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.
- 1mo ago First seen · 446 lines · 32 tokens per session scan A 73f90f5a19b8
Atlassian Requirements to Jira is an agent published in the GitHub repository github/awesome-copilot (40,401 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 3,974 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-30.
Other agents, from other repositories
ndv-scope
Scope enforcer. Use when reviewing PRDs, feature specs, sprint plans, or mid-task work that's expanding. Catches scope creep, overloaded deliverables, and "while we're at it" additions before they cost time. Autistic intolerance of undefined boundaries — undefined scope is not a risk to be managed, it is a state that…
product-owner
Strategic facilitator bridging business needs and technical execution. Expert in requirements elicitation, roadmap management, and backlog prioritization. Triggers on requirements, user story, backlog, MVP, PRD, stakeholder.
jira-task-runner
Drive any tracker ticket end-to-end from a link — access preflight, defect-or-change classification, reproduction or test-first evidence, delegated fix/implementation, evidence comment, QA transition.
phase-executor
Executes plans with deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator.
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.