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.
git clone --depth 1 https://github.com/grandcamel/JIRA-Assistant-SkillsWrote 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/commands/grandcamel/jira-assistant-skills/jira-discover-project)<a href="https://agentmods.dev/commands/grandcamel/jira-assistant-skills/jira-discover-project"><img src="https://agentmods.dev/badge/commands/grandcamel/jira-assistant-skills/jira-discover-project/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/commands/grandcamel/jira-assistant-skills/jira-discover-project"><img src="https://agentmods.dev/badge/commands/grandcamel/jira-assistant-skills/jira-discover-project.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.00016 | $0.01247 |
| Opus 5 | $0.00008 | $0.00624 |
| Sonnet 5 | $0.00003 | $0.00249 |
| Haiku 4.5 | $0.00002 | $0.00125 |
Grade B, and why
jira-discover-project scanned grade B with 1 finding 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 13d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/jira-project-{PROJECT_KEY}/defaults.json How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JIRA Project Discovery
You are helping the user discover and configure JIRA project context. This context enables intelligent defaults when creating issues.
What Gets Discovered
- Metadata: Issue types, components, versions, priorities, assignable users
- Patterns: Top assignees, common labels, and per-issue-type breakdowns based on recent activity
- Field usage: Per-field fill rates and value distributions (issue type, status, priority) from sampled issues
- Hierarchy: Parent hierarchy usage (how often sampled issues have a parent)
Step 1: Get Project Key
Ask the user which project they want to configure:
"Which JIRA project would you like to discover context for? Please provide the project key (e.g., PROJ, DEV, MYAPP)."
If the user provides multiple projects, handle them one at a time.
Step 2: Run Discovery
Run discovery with the jira-as CLI (credentials come from the environment or settings — run /jira-assistant-setup first if not configured):
jira-as ops discover-project {PROJECT_KEY}
Useful options:
| Option | Description |
|---|---|
-s, --sample-size N |
Number of issues to sample for patterns |
-d, --days N |
Sample period in days |
-o, --output [text|json] |
Output format (json returns the full discovery data) |
-v, --verbose |
Verbose output |
The command prints everything to stdout — it does not write any files. Capture the output.
Step 3: Review Results
After discovery completes, summarize what was found:
For the user, display:
- Number of issue types found
- Number of components found
- Number of versions
- Top assignees by activity
- Most common labels
- Field fill rates and value distributions worth noting
- Parent hierarchy usage
- Sample size and period
Example output:
Discovery complete for PROJ!
Discovered:
- 6 issue types: Bug, Story, Task, Epic, Subtask, Improvement
- 8 components: Backend, Frontend, API, Database, CI/CD, Docs, Testing, UX
- 3 versions: v2.1.0, v2.2.0, v3.0.0-beta
Patterns (last 30 days, 85 issues sampled):
- Top assignees: John Doe (35%), Jane Smith (28%), Bob Wilson (15%)
- Common labels: backend, needs-review, urgent, regression
- Priority distribution: High (45%), Medium (35%), Low (20%)
- Field fill rates: description 60%, components 40%, duedate 5%
- Parent hierarchy: 20% of sampled issues have a parent
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.
- 13d ago First seen · 152 lines · 16 tokens per session scan B f7e21d632061
jira-discover-project is a command published in the GitHub repository grandcamel/JIRA-Assistant-Skills (46 stars, last pushed 3d ago), licensed MIT. It adds 16 tokens to every session and 1,247 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
init-project
Initialize project with CLAUDE.md template - adaptive detection for new or existing projects.
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
handoff
Create a handoff document for seamless session continuity.
update-docs
Scan for recently modified files and update corresponding documentation.
create
Command "create" from freema/mcp-jira-stdio, covering /jira:create, usage, examples and what happens.
search
Search Jira issues using JQL.