JiraAgilePS: Instructions file for GitHub Copilot

.github/copilot-instructions.md

JiraAgilePS copilot-instructions.md is an instructions file for GitHub Copilot from AtlassianPS/JiraAgilePS. It costs 302 tokens per session, scanned A, original, MIT.

Coding instructions for GitHub Copilot working on the JiraAgilePS PowerShell module. They point Copilot to project rules, file locations, tests, documentation, and build checks.

In plain words
What is it for?
Guiding Copilot when editing PowerShell functions, Jira API code, tests, documentation, and release files.
Why use it?
They give the coding assistant a consistent source of repository conventions and validation steps.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file. Also seen: mentions AGENTS.md.

This is AtlassianPS/JiraAgilePS's own configuration. It tells GitHub Copilot how to work on JiraAgilePS itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything JiraAgilePS configures →

Reuse

Borrowing it

Nothing to install: this file belongs to AtlassianPS/JiraAgilePS. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/AtlassianPS/JiraAgilePS/master/.github/copilot-instructions.md
Clone the repo
git clone --depth 1 https://github.com/AtlassianPS/JiraAgilePS

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for JiraAgilePS copilot-instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/atlassianps/jiraagileps/copilot-instructions.svg)](https://agentmods.dev/instructions/atlassianps/jiraagileps/copilot-instructions)
Your own site
<a href="https://agentmods.dev/instructions/atlassianps/jiraagileps/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/atlassianps/jiraagileps/copilot-instructions.svg" alt="Measured on agentmods" height="20"></a>
Per session 302 This file is loaded in full into every session.
When invoked 302 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00302 $0.00302
Opus 5 $0.00151 $0.00151
Sonnet 5 $0.00060 $0.00060
Haiku 4.5 $0.00030 $0.00030

Measured 2d ago against content hash f1ff70c13511, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

JiraAgilePS copilot-instructions.md 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 2d 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.

.github/copilot-instructions.md · 24 lines

What it actually says

GitHub Copilot Entry Point

GitHub Copilot should treat these files as canonical:

Quick Reference

  1. Scope each change to one behavior; update tests/docs/changelog when impacted and available.
  2. Route Jira API interactions through Invoke-JiraMethod and preserve Cloud/Data Center behavior.
  3. During iteration, run targeted tests when present (for example Invoke-Pester -Path 'Tests/Functions/Public/Get-Board.Unit.Tests.ps1').
  4. Before finalizing, validate from repo root with ./Tools/setup.ps1 then Invoke-Build -Task Build, Test.
  5. This repo may have no Tests/; validation can warn/skip tests—report exact outcomes.
  6. Public function sources are unprefixed (for example Get-Board) and exported with JiraAgile prefix.

File Locations

  • Public functions: JiraAgilePS/Public/
  • Private functions: JiraAgilePS/Private/
  • Tests (optional legacy coverage): Tests/ (copied to Release/Tests/ when present)
  • Docs/help sources: docs/en-US/commands/ (add files when command help changes)
Changes

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.

  1. 2d ago First seen · 24 lines · 302 tokens per session scan A f1ff70c13511

Subscribe to this mod's changes

JiraAgilePS copilot-instructions.md is an instructions file published in the GitHub repository AtlassianPS/JiraAgilePS (3 stars, last pushed 6d ago), licensed MIT. It adds 302 tokens to every session, about $0.0015 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-09-04.

Related

Other instructions, from other repositories

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens