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.
curl -O https://raw.githubusercontent.com/AtlassianPS/JiraAgilePS/master/AGENTS.mdgit clone --depth 1 https://github.com/AtlassianPS/JiraAgilePSWrote 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/instructions/atlassianps/jiraagileps/agents-md)<a href="https://agentmods.dev/instructions/atlassianps/jiraagileps/agents-md"><img src="https://agentmods.dev/badge/instructions/atlassianps/jiraagileps/agents-md.svg" alt="Measured on agentmods" 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.01115 | $0.01115 |
| Opus 5 | $0.00558 | $0.00558 |
| Sonnet 5 | $0.00223 | $0.00223 |
| Haiku 4.5 | $0.00112 | $0.00112 |
Grade A, and why
JiraAgilePS AGENTS.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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Instructions for JiraAgilePS
Single source of truth for AI coding assistants. Tool-specific entry-point files in this repository reference this file.
Quick Reference (Critical Rules)
- Keep changes focused: scope each commit/PR to one behavior; include tests, docs, and changelog updates when impacted and available.
- Use the right test loop: during iteration, run targeted
Invoke-Pesterwhen relevant test files exist (for exampleInvoke-Pester -Path 'Tests/Functions/Public/Get-Board.Unit.Tests.ps1'). - Always attempt repo validation before finalizing: run
./Tools/setup.ps1andInvoke-Build -Task Build, Testfrom repo root. - Use shared Jira transport: route Jira API calls through
Invoke-JiraMethod. - Preserve compatibility: keep Jira Cloud/Data Center Agile behavior stable unless the change explicitly targets compatibility behavior.
- Do not overstate coverage: this repo may have no
Tests/folder; report skipped/failing validation clearly instead of claiming full test coverage. - Keep user-facing docs aligned: update
docs/en-US/commands/*.md(or add missing command pages when needed) andCHANGELOG.mdfor visible behavior changes.
AI Tool Compatibility
| Tool | Entry point | Canonical references |
|---|---|---|
| GitHub Copilot | .github/copilot-instructions.md |
AGENTS.md, .github/ai-context/powershell-rules.md |
| GitHub Copilot (file rules) | .github/instructions/jiraagile-api-compatibility.instructions.md |
.github/ai-context/powershell-rules.md |
| Cursor | .cursor/rules/jiraagileps.mdc |
AGENTS.md, .github/ai-context/powershell-rules.md |
| Claude Code | CLAUDE.md |
AGENTS.md, .github/ai-context/powershell-rules.md |
| Gemini/Antigravity | GEMINI.md |
AGENTS.md, .github/ai-context/powershell-rules.md |
Project Overview
JiraAgilePS adds Jira Agile cmdlets on top of JiraPS.
The repository is older and currently has less mature automated test coverage than JiraPS.
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.
- 2d ago First seen · 89 lines · 1,115 tokens per session scan A a31407fee958
JiraAgilePS AGENTS.md is an instructions file published in the GitHub repository AtlassianPS/JiraAgilePS (3 stars, last pushed 6d ago), licensed MIT. It adds 1,115 tokens to every session, about $0.0056 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.
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.
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).
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.
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.
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).
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.