Borrowing it
Nothing to install: this file belongs to letya999/jira-daily-pm-radar. 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/letya999/jira-daily-pm-radar/master/AGENTS.mdgit clone --depth 1 https://github.com/letya999/jira-daily-pm-radarWrote 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/letya999/jira-daily-pm-radar/agents-md)<a href="https://agentmods.dev/instructions/letya999/jira-daily-pm-radar/agents-md"><img src="https://agentmods.dev/badge/instructions/letya999/jira-daily-pm-radar/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.
<a href="https://agentmods.dev/instructions/letya999/jira-daily-pm-radar/agents-md"><img src="https://agentmods.dev/badge/instructions/letya999/jira-daily-pm-radar/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00353 | $0.00353 |
| Opus 5 | $0.00177 | $0.00177 |
| Sonnet 5 | $0.00071 | $0.00071 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
jira-daily-pm-radar 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 10d 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.
What it actually says
Agent Instructions
You are working in jira-daily-pm-radar, a Python 3.12 project built with uv.
Core idea
This project is an agent skill package for daily PM Jira radar:
- CLI does deterministic batch analysis
- MCP server exposes high-level tools for agents
- Skill explains when to use CLI/MCP and how to interpret output
- Reports are read-only and evidence-based
Do not
- Do not commit
.env, tokens, API keys, cookies, credentials, local reports, or raw Jira dumps. - Do not invent Jira data in tests or examples that looks like real company data.
- Do not make write operations to Jira unless a separate explicit feature is added and reviewed.
- Do not print tokens in logs.
Required checks before final answer or commit
Run:
uv run ruff format .
uv run ruff check .
uv run mypy src tests
uv run pytest
uv run bandit -r src
uv run python scripts/check_no_secrets.py
Architecture
Keep the agent-facing surface small:
SKILL.mdis a router, not an encyclopediareferences/00-agent-navigation.mdtells the agent which command/tool to use- CLI commands are stable and few:
doctor,daily,sprint,backlog,issue - MCP tools are high-level wrappers, not a raw Jira dump
Response style for generated PM summaries
Always answer:
- what changed
- what is stuck
- what smells
- what is poorly described
- what PM should do today
- where the HTML report is
- what data limitations exist
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.
- 10d ago First seen · 54 lines · 353 tokens per session scan A a0b2f666151f
jira-daily-pm-radar AGENTS.md is an instructions file published in the GitHub repository letya999/jira-daily-pm-radar (0 stars, last pushed 2mo ago), licensed MIT. It adds 353 tokens to every session, about $0.0018 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
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.
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).
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.
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).