agentmods.dev

mcp-jira-stdio: Instructions file for Codex

AGENTS.md

mcp-jira-stdio AGENTS.md is an instructions file for Codex, OpenCode from freema/mcp-jira-stdio. It costs 887 tokens per session, scanned A, original, MIT.

Repository instructions for an MCP server that connects AI assistants to Jira, a project-tracking service.

In plain words
What is it for?
Use them when developing Jira tools, checking credentials, building the TypeScript server, or running its tests and code checks.
Why use it?
They explain the source layout, commands, coding style, and testing process, reducing mistakes when changing the server.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is freema/mcp-jira-stdio's own configuration. It tells Codex and OpenCode how to work on mcp-jira-stdio 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 mcp-jira-stdio configures →

not rated 14repo 18d ago A scan 887 tokens original MIT
View source ↗ freema/mcp-jira-stdio
Reuse

Borrowing it

Nothing to install: this file belongs to freema/mcp-jira-stdio. 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/freema/mcp-jira-stdio/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/freema/mcp-jira-stdio

Made for: Codex, OpenCode.

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 mcp-jira-stdio AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/freema/mcp-jira-stdio/agents-md/github.svg)](https://agentmods.dev/instructions/freema/mcp-jira-stdio/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/freema/mcp-jira-stdio/agents-md"><img src="https://agentmods.dev/badge/instructions/freema/mcp-jira-stdio/agents-md/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.

agentmods 80×15 button for mcp-jira-stdio AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/freema/mcp-jira-stdio/agents-md"><img src="https://agentmods.dev/badge/instructions/freema/mcp-jira-stdio/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 887 This file is loaded in full into every session.
When invoked 887 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.00887 $0.00887
Opus 5.5 $0.00355 $0.00355
Sonnet 5.5 $0.00177 $0.00177
Haiku 4.5 $0.00089 $0.00089

Measured 1mo ago against content hash e43303d78457, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mcp-jira-stdio 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 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.

AGENTS.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository Guidelines

Project Structure & Modules

  • src/: TypeScript source.
    • index.ts: MCP server entry.
    • config/, tools/, types/, utils/: Configuration, MCP tools, shared types, helpers.
  • tests/: Vitest tests (unit/, optional integration/), plus mocks/ and fixtures/.
  • scripts/: Utility scripts (e.g., test-connection.cjs).
  • dist/: Build output (ESM). Do not edit.

Build, Test, and Development

  • npm run dev: Start in watch mode (tsx).
  • npm run build: Bundle with tsup to dist/.
  • npm start: Run built server.
  • npm run typecheck: TypeScript checks only.
  • npm run lint | lint:fix: ESLint (TypeScript + Prettier plugin).
  • npm run format | format:check: Prettier write/check.
  • npm test: Run Vitest. test:coverage for coverage, test:watch for watch.
  • npm run inspector | inspector:dev: Launch MCP Inspector (prod/dev).
  • Example: node scripts/test-connection.cjs verifies Jira credentials. Note: Node.js >= 18 required. task aliases exist in Taskfile.yaml if you prefer Task.

Coding Style & Naming

  • Language: TypeScript (ESM). Formatting via Prettier (2‑space indent). Lint via ESLint.
  • Types/interfaces: PascalCase (IssueType). Vars/functions: camelCase. Files: kebab-case in src/ (e.g., get-visible-projects.ts).
  • Unused params: prefix with _ to satisfy @typescript-eslint/no-unused-vars rule.
  • Console usage is allowed; keep logs purposeful and minimal.

Adding a Tool

  • Create src/tools/<name>.ts with a Tool export and handle<Name>.
  • Validate input in src/types/tools.ts via Zod and call validateInput(...) in the handler.
  • Export the tool from src/tools/index.ts and use TOOL_NAMES for consistent names.
  • Handlers are wired in src/index.ts using a TOOL_NAMES → handler map; the tool list is built from exports.
  • Return user-facing text via src/utils/formatters.ts and route errors through handleError.

Testing Guidelines

  • Framework: Vitest with V8 coverage. Thresholds: 80% (branches, functions, lines, statements).
  • Location: add tests under tests/unit/** (and tests/integration/** if needed).
  • Naming: *.test.ts. Use tests/mocks/ and tests/fixtures/ helpers; global setup in tests/setup.ts.
  • Run locally: npm test or npm run test:coverage before submitting.

Read the full file on GitHub · 66 lines

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. 1mo ago First seen · 66 lines · 887 tokens per session scan A e43303d78457

Subscribe to this mod's changes

mcp-jira-stdio AGENTS.md is an instructions file published in the GitHub repository freema/mcp-jira-stdio (14 stars, last pushed 18d ago), licensed MIT. It adds 887 tokens to every session, about $0.0035 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.

Claude Codeautomationjiramcpmcp-server
Related

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

microsoft/vscode · 9,649 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,384 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,159 tokens