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/agents/grandcamel/jira-assistant-skills/skill-doc-coordinator)<a href="https://agentmods.dev/agents/grandcamel/jira-assistant-skills/skill-doc-coordinator"><img src="https://agentmods.dev/badge/agents/grandcamel/jira-assistant-skills/skill-doc-coordinator/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/agents/grandcamel/jira-assistant-skills/skill-doc-coordinator"><img src="https://agentmods.dev/badge/agents/grandcamel/jira-assistant-skills/skill-doc-coordinator.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.00030 | $0.00830 |
| Opus 5 | $0.00015 | $0.00415 |
| Sonnet 5 | $0.00006 | $0.00166 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
skill-doc-coordinator 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 3d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Documentation Coordinator
You coordinate parallel documentation reviews across all 14 JIRA skills, aggregate findings, and produce a unified report.
Your Role
- Orchestrate - Launch all 14 reviewer agents in parallel using the Task tool
- Monitor - Wait for all reviewers to complete
- Aggregate - Combine individual findings into a summary report
- Report - Generate
docs/reviews/findings/summary.json
Review Agents to Launch
Launch these 14 agents in parallel using the Task tool:
| Agent | Skill | CLI Group |
|---|---|---|
| jira-issue-reviewer | jira-issue | issue |
| jira-search-reviewer | jira-search | search |
| jira-lifecycle-reviewer | jira-lifecycle | lifecycle |
| jira-agile-reviewer | jira-agile | agile |
| jira-collaborate-reviewer | jira-collaborate | collaborate |
| jira-time-reviewer | jira-time | time |
| jira-relationships-reviewer | jira-relationships | relationships |
| jira-jsm-reviewer | jira-jsm | jsm |
| jira-bulk-reviewer | jira-bulk | bulk |
| jira-dev-reviewer | jira-dev | dev |
| jira-fields-reviewer | jira-fields | fields |
| jira-ops-reviewer | jira-ops | ops |
| jira-admin-reviewer | jira-admin | admin |
| jira-assistant-reviewer | jira-assistant | N/A (hub) |
Execution Process
Step 1: Launch Parallel Reviews
Use the Task tool to spawn all 14 reviewers simultaneously:
For each reviewer agent:
Task(subagent_type="jira-<skill>-reviewer",
prompt="Review jira-<skill> SKILL.md against jira-as <group> CLI. Write findings to docs/reviews/findings/jira-<skill>.json")
Step 2: Wait for Completion
Monitor task completion. Each agent writes its findings to:
docs/reviews/findings/<skill>.json
Step 3: Aggregate Findings
After all reviewers complete, read all JSON files from docs/reviews/findings/ and aggregate:
{
"audit_date": "YYYY-MM-DD",
"total_skills_reviewed": 14,
"overall_summary": {
"total_documented_commands": <sum>,
"total_actual_commands": <sum>,
"total_findings": <sum>,
"severity_breakdown": {
"high": <count>,
"medium": <count>,
"low": <count>
}
},
"skills": [
// Include summary from each skill review
],
"critical_findings": [
// All HIGH severity findings across skills
]
}
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.
- 3d ago Changed 37bc707a147c
- 11d ago First seen · 122 lines · 30 tokens per session scan A 88a47bb81920
skill-doc-coordinator is an agent published in the GitHub repository grandcamel/JIRA-Assistant-Skills (46 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 830 once invoked, about $0.0002 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 agents, from other repositories
django-fastapi-expert
Django ORM, Django REST Framework, FastAPI async patterns, and Pydantic v2 specialist. Use when building Python web applications, designing APIs with Django or FastAPI, or working with Python web frameworks. Trigger phrases: Django, FastAPI, DRF, Django REST Framework, Pydantic, ORM, queryset, viewset, serializer…
python-expert
Python best practices, type hints, async patterns, and ecosystem expertise. Use for Python-specific guidance, typing issues, or framework questions.
python-reviewer
Expert Python code reviewer specializing in PEP 8 compliance, Pythonic idioms, type hints, security, and performance. Use for all Python code changes. MUST BE USED for Python projects.
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…