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 mostafa-drz/claude-skills --skill next-stepsgit clone --depth 1 https://github.com/mostafa-drz/claude-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/skills/mostafa-drz/claude-skills/next-steps)<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/next-steps"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/next-steps/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/mostafa-drz/claude-skills/next-steps"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/next-steps.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.00087 | $0.01523 |
| Opus 5.5 | $0.00035 | $0.00609 |
| Sonnet 5.5 | $0.00017 | $0.00305 |
| Haiku 4.5 | $0.00009 | $0.00152 |
Grade A, and why
next-steps 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 1mo 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next Steps — Stakeholder Alignment Checklist
What it does
Reads the current conversation (and optional connected context: Linear, Slack thread, Notion doc, git/PR state) and produces one consolidated checklist of next steps grouped by owner, ranked by priority, with explicit dependencies and open questions. Designed to be pasted into a Slack thread, a Linear comment, or a Notion update so everyone sees the same picture.
The point isn't to enumerate every possible task — it's to surface what unblocks the next move forward, so multiple stakeholders can self-serve.
When to use
- After a working session, before posting a status update.
- When a Slack/Linear thread has multiple unresolved threads — you need to consolidate.
- When the user says things like "so what are next steps", "align everyone on next items", "summarise what each person owes".
Do NOT use this for: timesheet recaps (use /workday-summary), retrospective
status posts (use /project-updates), or commit-by-commit breakdowns.
Inputs
Required:
- The current Claude conversation — the primary signal. The model already has this in context.
Optional (from the scope-hint arg or follow-up questions):
- A Linear ticket ID (e.g.
ENG-1234) — fetch viamcp__linear-server__get_issueto anchor scope and check current state/assignee. - A PR number (e.g.
#822) — fetch viagh pr viewfor state, reviewers, blocking checks. - A Slack thread permalink — read via Slack MCP to extract stakeholder asks.
- A Notion doc URL — read via WebFetch / Notion MCP for narrative context.
If the conversation already contains these references (it usually does), pull them automatically. Only ask the user when scope is genuinely ambiguous.
Workflow
1. Anchor the scope
Identify, in one sentence, what project / piece of work this is for. Pull it from the conversation. If multiple candidates exist, ask the user which one.
2. Identify stakeholders
List every named person and role that has appeared in the conversation or in referenced tickets/threads. Mark each as one of:
- Owner — has work to do
- Decider — owes a call/answer that unblocks others
- FYI — needs to know but has no action
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.
- 1mo ago Changed · +4 lines · +1 tokens per session fa257e58b48e
- 1mo ago First seen · 146 lines · 86 tokens per session scan A 9aaeec78faeb
next-steps is a skill published in the GitHub repository mostafa-drz/claude-skills (4 stars, last pushed yesterday), licensed MIT. It adds 87 tokens to every session and 1,523 once invoked, about $0.0003 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.
Other skills, from other repositories
wrap-up
Saves today's work session as a four-line entry (did, decided, open, next) at the top of the project's log.md, after the student confirms it, so a fresh chat can continue tomorrow with /pick-up. Writes to projects/ /log.md or career-vault/log.md, one entry per project touched, never to new-client. Use when the student…
pick-up
Reads the newest entry of a project's log.md and tells the student where they left off: what they did and decided, what is open, and the next step. Takes an optional project name. With several projects and no name, shows a menu of each project's last entry. Read only. Use when the student says pick up, where did I…
scrum-master-agent
Comprehensive Scrum Master assistant for sprint planning, backlog grooming, retrospectives, capacity planning, and daily standups with intelligent context-aware reporting.
shipkit-user-instructions
Use when there are manual tasks the user must complete. Triggers: 'create task', 'track TODO', 'user needs to', 'manual step required'.
codex-symphony
Install and operate a portable OpenAI Symphony + Linear orchestration setup in any Git repository. Use when the user wants a one-command local Symphony runner, a reusable WORKFLOW template, background launch scripts, or a Codex wrapper that restarts Symphony automatically when reopening the CLI.
shipkit-orchestrate
Core automation engine. Drives a set of steps to a confirmed ground-truth bar via a main-session delegate → reconcile → re-dispatch loop. Phase skills (build, review, direction) call it; can also run directly. Two modes: autonomous (run to done unattended) and steered (coordinate, surface to user). Triggers: invoked…