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/freema/mcp-jira-stdio/agents-mdgit clone --depth 1 https://github.com/freema/mcp-jira-stdioWrote 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/freema/mcp-jira-stdio/agents-md)<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="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.00887 | $0.00887 |
| Opus 5 | $0.00443 | $0.00443 |
| Sonnet 5 | $0.00177 | $0.00177 |
| Haiku 4.5 | $0.00089 | $0.00089 |
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 5d 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 — 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/, optionalintegration/), plusmocks/andfixtures/.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 withtsuptodist/.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:coveragefor coverage,test:watchfor watch.npm run inspector|inspector:dev: Launch MCP Inspector (prod/dev).- Example:
node scripts/test-connection.cjsverifies Jira credentials. Note: Node.js >= 18 required.taskaliases exist inTaskfile.yamlif 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 insrc/(e.g.,get-visible-projects.ts). - Unused params: prefix with
_to satisfy@typescript-eslint/no-unused-varsrule. - Console usage is allowed; keep logs purposeful and minimal.
Adding a Tool
- Create
src/tools/<name>.tswith aToolexport andhandle<Name>. - Validate input in
src/types/tools.tsvia Zod and callvalidateInput(...)in the handler. - Export the tool from
src/tools/index.tsand useTOOL_NAMESfor consistent names. - Handlers are wired in
src/index.tsusing aTOOL_NAMES→ handler map; the tool list is built from exports. - Return user-facing text via
src/utils/formatters.tsand route errors throughhandleError.
Testing Guidelines
- Framework: Vitest with V8 coverage. Thresholds: 80% (branches, functions, lines, statements).
- Location: add tests under
tests/unit/**(andtests/integration/**if needed). - Naming:
*.test.ts. Usetests/mocks/andtests/fixtures/helpers; global setup intests/setup.ts. - Run locally:
npm testornpm run test:coveragebefore submitting.
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.
- 5d ago First seen · 66 lines · 887 tokens per session scan A e43303d78457
mcp-jira-stdio AGENTS.md is an instructions file published in the GitHub repository freema/mcp-jira-stdio (14 stars, last pushed 2d ago), licensed MIT. It adds 887 tokens to every session, about $0.0044 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-30.
Other instructions, from other repositories
ultra-jira-mcp CLAUDE.md
Claude Code instructions for criblio/ultra-jira-mcp, covering ultra-jira-mcp — agent guide, layout, mental model, two modes — pick the right one and what lives where (toolkit vs. this repo).
ultra-jira-mcp AGENTS.md
AGENTS.md instructions for criblio/ultra-jira-mcp, covering agents.md and quick reference.
jayrah AGENTS.md
Instructions for chmouel/jayrah, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
jayrah web-ui.instructions.md
Instructions for chmouel/jayrah, covering web ui development instructions, development workflow, running the web server, file structure and key features implemented.
jayrah tui.instructions.md
Instructions for chmouel/jayrah, a project described as: 🌞 Jayrah - Jira Terminal and web user interface and AI-powered command palette (MCP) 🌞.
jayrah CLAUDE.md
Instructions for chmouel/jayrah, a project described as: 🌞 Jayrah - Jira Terminal and web user interface and AI-powered command palette (MCP) 🌞.