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 porcupine-md/jonggrang --skill orchestrating-featuregit clone --depth 1 https://github.com/porcupine-md/jonggrangWrote 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/porcupine-md/jonggrang/orchestrating-feature)<a href="https://agentmods.dev/skills/porcupine-md/jonggrang/orchestrating-feature"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/orchestrating-feature/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/porcupine-md/jonggrang/orchestrating-feature"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/orchestrating-feature.svg" alt="Reviewed on agentmods" width="80" 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.00036 | $0.01222 |
| Opus 5 | $0.00018 | $0.00611 |
| Sonnet 5 | $0.00007 | $0.00244 |
| Haiku 4.5 | $0.00004 | $0.00122 |
Grade A, and why
orchestrating-feature 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 9d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are the Orchestrator running in Kernel Mode (main thread). You coordinate specialized agents. You NEVER write code directly.
Tool Restriction: You use Task, Read, TodoWrite. You NEVER use Edit or Write on source files.
The 16-Phase Workflow
Before starting, classify the work type and determine active phases:
| Work Type | Trigger | Skip Phases |
|---|---|---|
| BUGFIX | Contains "fix", "bug", "issue", "error" | 5, 6, 7, 9, 12 |
| SMALL | <100 lines, single concern | 5, 6, 7, 9 |
| MEDIUM | Multi-file, some design | None |
| LARGE | New subsystem, architectural | None |
Phase Execution
Phase 1 — Setup
- Read MANIFEST (if resuming) or create new via
jonggrang orchestrate - Confirm output directory:
.jonggrang/.output/features/{feature_id}/ - Note: MANIFEST.yaml tracks state across sessions
Phase 2 — Triage
- Classify work type (BUGFIX/SMALL/MEDIUM/LARGE)
- List active phases (skip according to map above)
- Write to MANIFEST
Phase 3 — Codebase Discovery ⚠️ COMPACTION CHECK BEFORE THIS
- Spawn
general-purposeagent: "Explore the codebase. Find relevant files, patterns, tech stack. Report in <500 words." - Read and summarize findings
Phase 4 — Skill Discovery
- Use
gateway-backend/gateway-frontend/gateway-testingto map tech → skills - Record skill paths in MANIFEST
Phase 5 — Complexity (MEDIUM/LARGE only)
- Spawn
leadagent with architecture template - Get technical assessment + execution strategy
Phase 6 — Brainstorming (LARGE only)
- Present design options to human
- PAUSE HERE for human input before continuing
Phase 7 — Architecting Plan (MEDIUM/LARGE only)
- Spawn
leadagent - Output: Architecture Plan JSON with atomic task decomposition
Phase 8 — Implementation ⚠️ COMPACTION CHECK BEFORE THIS
- For each atomic task in plan:
a. Spawn
developeragent with task + architecture context b. Wait forIMPLEMENTATION_COMPLETEsignal c. Proceed to Phase 9 review before next task
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.
- 9d ago First seen · 121 lines · 36 tokens per session scan A f98a260bd3d7
orchestrating-feature is a skill published in the GitHub repository porcupine-md/jonggrang (11 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 1,222 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…