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 skills add hieptran87/atlassian-mcp-server --skill jira-sprint-dashboard-canvasgit clone --depth 1 https://github.com/hieptran87/atlassian-mcp-serverWrote 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/skills/hieptran87/atlassian-mcp-server/jira-sprint-dashboard-canvas)<a href="https://agentmods.dev/skills/hieptran87/atlassian-mcp-server/jira-sprint-dashboard-canvas"><img src="https://agentmods.dev/badge/skills/hieptran87/atlassian-mcp-server/jira-sprint-dashboard-canvas/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/skills/hieptran87/atlassian-mcp-server/jira-sprint-dashboard-canvas"><img src="https://agentmods.dev/badge/skills/hieptran87/atlassian-mcp-server/jira-sprint-dashboard-canvas.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.00112 | $0.03352 |
| Opus 5 | $0.00056 | $0.01676 |
| Sonnet 5 | $0.00022 | $0.00670 |
| Haiku 4.5 | $0.00011 | $0.00335 |
Grade A, and why
jira-sprint-dashboard 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 12d 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.
This is a copy
100% identical to jira-sprint-dashboard — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Sprint Dashboard
Build a focused dashboard that helps an engineering manager, tech lead, or senior engineer see current Jira work quickly enough to decide what needs attention. The output is a dashboard, not a prose report and not a generic health score.
This skill is read-only by default. Do not create, update, transition, assign, or comment on Jira work items unless the user explicitly asks for a write action after reviewing the dashboard.
Output Mode
Use the richest dashboard renderer supported by the current environment. The dashboard content, claims, counts, and source appendix must stay consistent across renderers; only the presentation changes.
Choose the renderer in this order:
- Cursor Canvas, if running in Cursor with Canvas support.
- Interactive artifact, if the current agent supports HTML, React, or similar artifact output.
- Static HTML file, if file creation is available and useful.
- Markdown dashboard, if no richer visual renderer is available.
- Structured JSON plus concise summary, only if visual rendering is impossible.
Do not mention that Cursor Canvas is unavailable unless the user specifically asked for Cursor Canvas. If the user asked for a dashboard generally, use the best available renderer without apologizing for the environment.
Cursor Canvas Renderer
Use this section only when running in Cursor with Canvas support.
Read ~/.cursor/skills-cursor/canvas/SKILL.md before writing canvas code. If
you need exact exports or prop shapes, read the files in
~/.cursor/skills-cursor/canvas/sdk/.
Canvas constraints:
- Create one
.canvas.tsxfile in the Cursor canvases directory. - Import only from
cursor/canvas. Do not importreact,CSSProperties,JSX, Atlaskit, or other packages. - Embed Jira data inline in the canvas; do not fetch from the canvas.
- Prefer Canvas primitives such as
Stack,Grid,Card,Stat,Table,Pill,Callout,UsageBar,BarChart,LineChart,PieChart, andCodeover raw HTML. - Use
useHostTheme()for custom styles. Do not hardcode hex colors, gradients, box shadows, ADS variables, unsupported CSS frameworks, or@atlaskit/*. - Do not publish or share the canvas unless the user asks.
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.
- 12d ago First seen · 357 lines · 112 tokens per session scan A 3e78ef20541e
jira-sprint-dashboard is a skill published in the GitHub repository hieptran87/atlassian-mcp-server (0 stars, last pushed 1mo ago), licensed MIT. It adds 112 tokens to every session and 3,352 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to jira-sprint-dashboard, differing in 12 lines, and is treated as a copy.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.