agentmods.dev

NutriSport: Skill for Claude Code

.claude/skills/orchestrate-features/SKILL.md

orchestrate-features is a skill for Claude Code from satanyakiv/NutriSport. It costs 66 tokens per session (651 once invoked), scanned A, original, MIT.

A workflow for coordinating several software features through separate working directories, called worktrees, so agents can develop them in parallel. It defines feature groups, dependencies, merge order, and test work.

In plain words
What is it for?
Use it to run all planned feature groups, run one group, start selected features, check feature status, or execute the specified feature and testing sequence.
Why use it?
It helps manage large batches of feature work without losing track of which tasks can run together and which must wait for earlier changes.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

This is satanyakiv/NutriSport's own configuration. It tells Claude Code how to work on NutriSport itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything NutriSport configures →

not rated 11repo 5mo ago A scan 66 tokens original MIT
View source ↗ satanyakiv/NutriSport
Reuse

Borrowing it

Nothing to install: this file belongs to satanyakiv/NutriSport. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/satanyakiv/NutriSport/main/.claude/skills/orchestrate-features/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/satanyakiv/NutriSport

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 orchestrate-features

README.md
[![agentmods](https://agentmods.dev/badge/skills/satanyakiv/nutrisport/orchestrate-features/github.svg)](https://agentmods.dev/skills/satanyakiv/nutrisport/orchestrate-features)
Your own site
<a href="https://agentmods.dev/skills/satanyakiv/nutrisport/orchestrate-features"><img src="https://agentmods.dev/badge/skills/satanyakiv/nutrisport/orchestrate-features/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 orchestrate-features

Your own site · 80×15
<a href="https://agentmods.dev/skills/satanyakiv/nutrisport/orchestrate-features"><img src="https://agentmods.dev/badge/skills/satanyakiv/nutrisport/orchestrate-features.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 651 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.00066 $0.00651
Opus 5.5 $0.00026 $0.00260
Sonnet 5.5 $0.00013 $0.00130
Haiku 4.5 $0.00007 $0.00065

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

Security

Grade A, and why

orchestrate-features 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/orchestrate-features/SKILL.md · 63 lines

How it starts

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

orchestrate-features

Orchestrate feature implementation using parallel worktree agents.

Usage

/orchestrate-features all           — run all groups (A, B, C, D, then E)
/orchestrate-features group:A       — run Group A features (01, 03, 10)
/orchestrate-features group:B       — run Group B features (04→06→05→07)
/orchestrate-features 01,03         — run specific features by number
/orchestrate-features status        — show status of all features

Prompt

You are orchestrating NutriSport feature implementation. Read the orchestrator and feature files first:

  1. Read .claude/features/00-orchestrator.md for parallel groups, merge order, and conflict matrix
  2. Read .claude/rules/plan-mode.md for status conventions
  3. Read the specific feature file(s) from .claude/features/

For all:

Launch agents for Groups A, B, C, D in parallel (each in a worktree). Wait for all to complete. Then launch Group E (tests).

For group:X:

Launch agent(s) for the specified group:

  • Group A: Launch 3 parallel agents (01, 03, 10 — no conflicts)
  • Group B: Launch 1 agent doing 04→06→05→07 sequentially
  • Group C: Launch 1 agent doing 09→08 sequentially
  • Group D: Launch 1 agent doing 11→12 sequentially
  • Group E: Launch 1 agent doing 02 (tests for everything)

For specific numbers (e.g., 01,03):

Check conflict matrix. If no conflicts, launch in parallel worktrees. If conflicts exist, run sequentially.

For status:

Read all feature files and report their Status field in a table.

Agent pattern:

Agent(
  subagent_type="general-purpose",
  isolation="worktree",
  prompt="Implement feature NN. Read .claude/features/NN-name.md for full spec. Follow .claude/rules/ for conventions. Update feature file status to IN_PROGRESS at start and IMPLEMENTED when done."
)

After completion:

  1. Update feature file status to IMPLEMENTED
  2. Report results: files created/modified, tests passing, build status
  3. If merge needed, provide merge commands (do NOT auto-merge without user confirmation)

Read the full file on GitHub · 63 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 · 63 lines · 66 tokens per session scan A e5fae8b5316a

Subscribe to this mod's changes

orchestrate-features is a skill published in the GitHub repository satanyakiv/NutriSport (11 stars, last pushed 5mo ago), licensed MIT. It adds 66 tokens to every session and 651 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-30.

Git and workflowProject management
Related

Other skills, from other repositories

antfu-issue-triage

Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…

antfu/skills · 76 tokens

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

engineer-bot-ops

A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.

makecindy/cindy · 57 tokens

shiplog

Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.

aeonfun/aeon · 46 tokens

llxprt-issue-workflow

Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…

vybestack/llxprt-code · 88 tokens

connect

Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…

nimbalyst/nimbalyst · 101 tokens