agentmods.dev

jira-cli AGENTS.md

Repository instructions for the `jira-cli` command-line tool, including which project specifications to read and which files must stay synchronized.

In plain words
What is it for?
Use them when modifying or releasing `jira-cli`, especially its CLI output, bundled skills, security rules, documentation, end-to-end tests, or changelog.
Why use it?
They give an agent the rules needed to make consistent changes and preserve the tool’s command behavior, security requirements, tests, and release checks.

Instructions file for CodexOpenCode

5 7d ago A scan 252 tokens original MIT
View the source file fatecannotbealtered/jira-cli
Install

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.

agentmods
npx agentmods add instructions/fatecannotbealtered/jira-cli/agents-md
Clone the repo
git clone --depth 1 https://github.com/fatecannotbealtered/jira-cli

Made for: Codex, OpenCode.

Per session 252 This file is loaded in full into every session.
When invoked 252 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00252 $0.00252
Opus 5 $0.00126 $0.00126
Sonnet 5 $0.00050 $0.00050
Haiku 4.5 $0.00025 $0.00025

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

Security

Grade A, and why

jira-cli 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.

AGENTS.md · 18 lines

What it actually says

Agent Entry

This repository follows the reusable AI-native tool specs in .agent/.

Start with .agent/AGENT.md, then read only the spec relevant to the task:

  • .agent/CLI-SPEC.md for CLI output, errors, write confirmation, and self-description.
  • .agent/SKILL-SPEC.md for bundled Skill behavior.
  • Shared REPO-SPEC.md for repository layout and release conventions.
  • .agent/SEC-SPEC.md for security tier, credential, injection, and supply-chain rules.

For this tool, keep the CLI contract, README files, skills/jira-cli/SKILL.md, E2E scripts, and CHANGELOG.md synchronized in the same change.

Before release, Functional Contract Coverage must remain 100%: every public README / Skill / reference / help / context / doctor / changelog / update behavior needs command-level tests.

Release readiness must be explicit: reference.release_readiness and doctor declare stable, beta, or unpublishable; stable requires recorded live smoke/E2E evidence.

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 · 18 lines · 252 tokens per session scan A e5abb9401445

Subscribe to this mod's changes

jira-cli AGENTS.md is an instructions file published in the GitHub repository fatecannotbealtered/jira-cli (5 stars, last pushed 7d ago), licensed MIT. It adds 252 tokens to every session, about $0.0013 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.

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 · 6,785 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

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

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,345 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

next.js 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