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 jayminwest/seeds --skill seeds-issue-workflowgit clone --depth 1 https://github.com/jayminwest/seedsWrote 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/jayminwest/seeds/seeds-issue-workflow)<a href="https://agentmods.dev/skills/jayminwest/seeds/seeds-issue-workflow"><img src="https://agentmods.dev/badge/skills/jayminwest/seeds/seeds-issue-workflow.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00056 | $0.00792 |
| Opus 5 | $0.00028 | $0.00396 |
| Sonnet 5 | $0.00011 | $0.00158 |
| Haiku 4.5 | $0.00006 | $0.00079 |
Grade A, and why
seeds-issue-workflow 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 8d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
seeds-issue-workflow
Use this skill inside the seeds repo when you need to turn a vague ask
into a tracked unit of work that sd ready will surface. It encodes
two procedures: create-then-ready for a single scoped task, and
plan-decomposition for work large or ambiguous enough that an LLM
benefits from structured breakdown first.
Pre-flight
sd prime # inject rules + command reference
sd ready # see what is already unblocked
sd search "<keywords>" # avoid filing a duplicate
If a seed already covers the work, claim it
(sd update <id> --status in_progress) instead of filing a new one.
Procedure A — create-then-ready (single scoped task)
For a task that fits in one focused commit:
sd create --title "Fix sd close race on concurrent writers" \
--type bug --priority 1 \
--description "Two agents closing the same id can drop one update."
Capture the printed id (e.g. seeds-1a2b), then tag and wire it:
sd label add seeds-1a2b concurrency
sd dep add seeds-1a2b seeds-9f8e # this work depends on seeds-9f8e first
A seed is ready when it is open and every id in its blockedBy
list is closed. Add dependencies for real ordering only — every
unnecessary sd dep add hides the work from sd ready. Verify:
sd ready | grep seeds-1a2b # appears once its blockers close
Procedure B — plan-decomposition (large / ambiguous work)
When the work is multi-step, emit a structured prompt, fill it, and let seeds spawn the children:
sd plan prompt seeds-1a2b > /tmp/plan.json # emit the template to fill
$EDITOR /tmp/plan.json # write one step per unit of work
sd plan submit seeds-1a2b --plan /tmp/plan.json
Each step becomes one child seed; a step's blocks: [j] wires step
i's id into step j's blockedBy, so the children come out in
dependency order. Steps may carry labels: [...] that flow to the
spawned child (normalized and merged additively). Inspect and track:
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.
- 8d ago First seen · 91 lines · 56 tokens per session scan A 27cf2cd76800
seeds-issue-workflow is a skill published in the GitHub repository jayminwest/seeds (132 stars, last pushed 6d ago), licensed MIT. It adds 56 tokens to every session and 792 once invoked, about $0.0003 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.