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.
npx agentmods add instructions/choplin/jira-cli-mcp/claude-mdgit clone --depth 1 https://github.com/choplin/jira-cli-mcpWrote 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/choplin/jira-cli-mcp/claude-md)<a href="https://agentmods.dev/instructions/choplin/jira-cli-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/choplin/jira-cli-mcp/claude-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.01138 | $0.01138 |
| Opus 5 | $0.00569 | $0.00569 |
| Sonnet 5 | $0.00228 | $0.00228 |
| Haiku 4.5 | $0.00114 | $0.00114 |
Grade A, and why
jira-cli-mcp CLAUDE.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 6d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira CLI MCP Server Project Memory
Project Overview
MCP (Model Context Protocol) server that wraps the jira-cli command-line tool to enable AI assistants to interact
with Jira.
Key Features
-
list_tickets - Search and list Jira tickets with semantic filters
- Supports JQL queries and semantic parameters (assignedToMe, status, project, etc.)
- Status enum includes: "open", "in progress", "in review", "done", "closed", "todo", "to do"
-
get_ticket - Get detailed ticket information
- Parses ADF (Atlassian Document Format) to Markdown
- Includes comments with pagination support
-
update_ticket_description - Update ticket descriptions
- Accepts Markdown input (converted to ADF by jira-cli)
-
add_comment - Add comments to tickets
- Supports rich text formatting via Markdown
-
assign_to_me - Assign tickets to current user
- Uses
jira mecommand to get current user
- Uses
-
move_ticket - Move tickets between statuses
- Maps lowercase status names to Jira status names
-
open_ticket_in_browser - Open tickets in default web browser
- Uses
jira opencommand to launch browser
- Uses
Technical Details
- Runtime: Bun
- Language: TypeScript (strict mode, no
anytypes) - Testing: Separated unit tests (mocked) and integration tests
- Code Quality: Biome for linting/formatting, lefthook for git hooks
- Type Safety: Centralized status definitions in
src/utils/types.ts
Project Structure
src/
├── index.ts # MCP server entry point
├── config.ts # Configuration management
├── tools/ # MCP tool implementations
└── utils/ # Shared utilities
├── types.ts # Common types and status definitions
├── jiraExecutor.ts # jira-cli command wrapper
└── adf-types.ts # Atlassian Document Format types
tests/
├── *.test.ts # Unit tests with mocks
└── integration/ # Integration tests with real jira-cli
Environment Variables
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.
- 6d ago First seen · 139 lines · 1,138 tokens per session scan A c468e16e0094
jira-cli-mcp CLAUDE.md is an instructions file published in the GitHub repository choplin/jira-cli-mcp (9 stars, last pushed 1y ago), licensed MIT. It adds 1,138 tokens to every session, about $0.0057 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-08-31.
Other instructions, from other repositories
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).
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 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.
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.