agentmods.dev

jira-progress-pulse

jira-progress-pulse is a skill for Claude Code from Aibier/claude-em-toolkit. It costs 41 tokens per session (595 once invoked), scanned A, original, MIT.

A scheduled progress report that compares Jira or Linear project tasks with the previous run and sends important changes to Slack. Jira and Linear are tools for tracking software work; Slack is a team messaging app.

In plain words
What is it for?
Use it twice a day to report items that became blocked, entered review, were completed, or are due soon, using connected official Jira or Linear services.
Why use it?
Teams can miss blockers, status changes, and approaching deadlines when updates are scattered across task trackers. This produces a short alert about meaningful movement instead of making people scan every task.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

not rated 5repo 5mo ago A scan 41 tokens original MIT

Good fit Use it twice a day to report items that became blocked, entered review, were completed, or are due soon, using connected official Jira or Linear services.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aibier/claude-em-toolkit/jira-progress-pulse
View source ↗ Aibier/claude-em-toolkit
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.

Any agent
npx skills add Aibier/claude-em-toolkit --skill jira-progress-pulse
Clone the repo
git clone --depth 1 https://github.com/Aibier/claude-em-toolkit

Made for: Claude Code.

Wrote 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.

agentmods badge for jira-progress-pulse

README.md
[![agentmods](https://agentmods.dev/badge/skills/aibier/claude-em-toolkit/jira-progress-pulse/github.svg)](https://agentmods.dev/skills/aibier/claude-em-toolkit/jira-progress-pulse)
Your own site
<a href="https://agentmods.dev/skills/aibier/claude-em-toolkit/jira-progress-pulse"><img src="https://agentmods.dev/badge/skills/aibier/claude-em-toolkit/jira-progress-pulse/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.

agentmods 80×15 button for jira-progress-pulse

Your own site · 80×15
<a href="https://agentmods.dev/skills/aibier/claude-em-toolkit/jira-progress-pulse"><img src="https://agentmods.dev/badge/skills/aibier/claude-em-toolkit/jira-progress-pulse.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 595 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00041 $0.00595
Opus 5.5 $0.00016 $0.00238
Sonnet 5.5 $0.00008 $0.00119
Haiku 4.5 $0.00004 $0.00060

Measured 2mo ago against content hash e5fb57644786, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

jira-progress-pulse 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 2mo 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.

.claude/skills/jira-progress-pulse/SKILL.md · 51 lines

How it starts

The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Jira/Linear → Slack Progress Pulse

Runs twice daily (morning/EOD) as a scheduled routine. Pulls task state from Jira or Linear, identifies what actually matters to an EM, and posts a short Slack alert — not a full dump.

Steps

  1. Pull current state via the official MCP servers — don't scrape or hand-roll API calls; the official connectors handle auth, pagination, and stay current with the API:

    • Linear MCP (linear plugin / official Linear MCP server): list_issues filtered by team/project, list_cycles for the active cycle
    • Atlassian MCP (official Atlassian Remote MCP server, ships Jira + Confluence tools): searchJiraIssuesUsingJql with a JQL scoped to the project + sprint
    • Compare against the previous run (keep a small state note — e.g. last-seen status per issue — so you can detect changes, not just current state)
    • If neither MCP server is connected, say so explicitly and point to setup (claude mcp add / Settings → Connectors) rather than falling back to scraping or asking the user for raw API tokens.

  2. Filter for what's "key progress", not noise:

    • Status transitions into/out of "Blocked", "In Review", "Done"
    • Items due within 2 days that are not yet in progress
    • New high-priority issues created since the last pull
    • Anything that moved backward (e.g. Done → In Progress)

  3. Draft a short Slack message (not a wall of text):

    📊 Project Pulse — <project> (<AM/PM>)
✅ Done: <issue keys/titles, max 3>
🚧 Newly blocked: <issue keys — flag these first, an EM cares most here>
⏰ Due soon, not started: <issue keys>

    Omit any section with nothing to report — don't pad.

  4. Send via the configured Slack integration/webhook. If no Slack MCP/integration is connected yet, say so and show the drafted message instead of failing silently.

Notes

  • This is a scheduled routine — set it up with /schedule (runs this skill twice daily, e.g. 9am and 5pm) rather than running it ad hoc.
  • Keep the alert skimmable in <10 seconds; link out to Jira/Linear for detail.
  • Never invent status changes — only report what the API actually returned.

Read the full file on GitHub · 51 lines

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. 2mo ago First seen · 51 lines · 41 tokens per session scan A e5fb57644786

Subscribe to this mod's changes

jira-progress-pulse is a skill published in the GitHub repository Aibier/claude-em-toolkit (5 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 595 once invoked, about $0.0002 per session on Opus 5.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.

Project management
Related

Other skills, from other repositories

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

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…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

dev-console-context

Use when the user mentions Developer Console, projects, workspaces, credentials, or orgs — or uses phrases like "show my projects", "list workspaces", "get credentials", "switch project", "which org", "my org", "console", "navigate", "explore", "what projects do I have", "show credentials", "what workspace". Also use…

adobe/skills · 169 tokens

ring:mapping-feature-relationships

Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…

LerianStudio/ring · 104 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens