A scheduled queue watcher for MorningStar, a workflow that processes product requirement documents. It checks Notion and Jira for pending work, starts a GitHub Actions workflow, and posts a summary to Slack.

Use it to scan for pending MorningStar PRDs, trigger their GitHub Actions processing, and report the result to Slack.

It removes the need to check several work-tracking systems and start the processing workflow manually.

watch — Skill for Claude Code by lonexreb

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 lonexreb/morningstar --skill watch

Clone the repo

git clone --depth 1 https://github.com/lonexreb/morningstar

Made for: Claude Code.

Or install morningstar, the plugin that ships this one along with the rest of its 5 skills, 1 agent.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/lonexreb/morningstar/watch/github.svg)](https://agentmods.dev/skills/lonexreb/morningstar/watch)

Your own site

<a href="https://agentmods.dev/skills/lonexreb/morningstar/watch"><img src="https://agentmods.dev/badge/skills/lonexreb/morningstar/watch/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/lonexreb/morningstar/watch"><img src="https://agentmods.dev/badge/skills/lonexreb/morningstar/watch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 101 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 793 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.

Model	Per session	Once invoked
Fable 5.1	$0.00101	$0.00793
Opus 5	$0.00051	$0.00396
Sonnet 5	$0.00020	$0.00159
Haiku 4.5	$0.00010	$0.00079

Measured 10d ago against content hash 7440dd206597, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

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

skills/watch/SKILL.md · 79 lines

How it starts

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

Watch the MorningStar queue

Poll the Notion DB and Jira project for pending PRDs. If any are found, dispatch the morningstar-scheduled.yml GitHub Actions workflow and post a summary to Slack.

Arguments

User provided: $ARGUMENTS

Optional:

--repo (default: lonexreb/morningstar): GitHub owner/name for the executor workflow.

Prerequisites the user has configured

MORNINGSTAR_NOTION_DB_ID, MORNINGSTAR_NOTION_TOKEN (environment) -- for the Notion DB scan.
MORNINGSTAR_JIRA_URL, MORNINGSTAR_JIRA_EMAIL, MORNINGSTAR_JIRA_TOKEN, MORNINGSTAR_JIRA_PROJECT_KEY -- for Jira.
gh CLI authenticated (any of: GH_TOKEN env, gh auth login, or the Claude Code GitHub MCP).
MORNINGSTAR_SLACK_WEBHOOK -- for the summary post.

Instructions

Scan Notion using the Notion MCP tool:
- Query database $MORNINGSTAR_NOTION_DB_ID
- Filter: Status == "Pending"
- Collect the row IDs and titles.
Scan Jira via WebFetch (or Jira MCP if installed):
- GET $MORNINGSTAR_JIRA_URL/rest/api/3/search?jql=project = $MORNINGSTAR_JIRA_PROJECT_KEY AND labels = "morningstar" AND status = "To Do"
- Basic auth with $MORNINGSTAR_JIRA_EMAIL / $MORNINGSTAR_JIRA_TOKEN.
- Collect issue keys + summaries.
Decide:
- If both lists are empty: post MorningStar watcher: no pending items. to Slack via webhook. Exit.
- If non-empty: continue.

Dispatch the executor:

gh workflow run morningstar-scheduled.yml --repo <target-repo> --field force_run=true

Report the run URL if gh returns one.

Post Slack summary:

MorningStar watcher: N pending items queued.
- Notion: <count> (titles...)
- Jira: <count> (issue keys...)
Executor dispatched: <run URL>

Exit quickly -- this skill must stay under ~30 seconds so it's cheap to schedule.

Recommended cadence

/schedule morningstar:watch --cron "0 * * * *"

Read the full file on GitHub · 79 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.

10d ago First seen · 79 lines · 101 tokens per session scan A 7440dd206597

Subscribe to this mod's changes

watch is a skill published in the GitHub repository lonexreb/morningstar (1 stars, last pushed 4mo ago), licensed MIT. It adds 101 tokens to every session and 793 once invoked, about $0.0005 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.

Project management ai-agent anthropic-claude automation autonomous-agent background-agent

planner

Interactive planning and execution for complex tasks. Use when breaking down multi-step projects (planning) or executing approved plans through delegation (execution). Planning creates milestones with specifications; execution delegates to specialized agents. Use when you say "plan this feature", "create…

rjmurillo/ai-agents · 60 tokens

execution-plans

Manage execution plans as versioned artifacts with progress tracking and decision logs. Use when you say "create execution plan", "update plan progress", "log decision", "complete plan", or "abandon plan". Do NOT use to break work into milestones or delegate tasks (use planner).

rjmurillo/ai-agents · 61 tokens

work-operating-model

Run a 5-layer interview to elicit how a team actually works (rhythms, decisions, dependencies, institutional knowledge, friction) and emit a structured operating model. Use when you say "elicit operating model", "interview team operating model", "how does this team actually work", or "validate operating model". Do NOT…

rjmurillo/ai-agents · 102 tokens

retro

Fill an unfilled auto-retrospective skeleton for a date, or list the skeletons still pending. Use when you say retro fill, fill retro skeleton, or list pending retros. Do NOT use to run the retrospective analysis itself (this hands off to the retrospective skill), and do NOT use to write a session log.

rjmurillo/ai-agents · 70 tokens

ai-agents-docs-of-record

Runbook for this repo's documents of record. Session logs, ADRs, retrospectives, Serena memories, per-issue handoffs, plus the templates, validators, naming rules, and house prose style that bind them. Use when you say write the session log, create an ADR, fill the retro, save this to memory, which document of record.…

rjmurillo/ai-agents · 113 tokens

swarm-manager-backlog-tools

Canonical reference for the swarm-manager backlog item data model and interaction patterns. All skills that read or write backlog item artifacts should defer to this document for folder structure, artifact schemas, reading order, CLI commands, and mutation rules.

Vrooli/Vrooli · 0 tokens