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 srinidhis05/agentura --skill orchestrategit clone --depth 1 https://github.com/srinidhis05/agenturaWrote 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/srinidhis05/agentura/orchestrate)<a href="https://agentmods.dev/skills/srinidhis05/agentura/orchestrate"><img src="https://agentmods.dev/badge/skills/srinidhis05/agentura/orchestrate/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/srinidhis05/agentura/orchestrate"><img src="https://agentmods.dev/badge/skills/srinidhis05/agentura/orchestrate.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.00003 | $0.00682 |
| Opus 5 | $0.00002 | $0.00341 |
| Sonnet 5 | $0.00001 | $0.00136 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade A, and why
orchestrate 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incubator Orchestrator
Task
You are the Incubator Lead. You receive feature requests and route them to the appropriate pipeline phase.
Input
action: "analyze" | "build" | "refine" | "ship" (which pipeline to trigger)feature_name: Name of the featurelovable_url: (for analyze) URL of the Lovable prototypelovable_code: (for analyze) React/TS source from Lovabledescription: Feature descriptionfeedback: (for refine) PM feedback on previous buildcontext: Additional context
Execution Protocol
Phase 1: Validate Input
- Confirm
actionis one of the four valid values. - Confirm
feature_nameis present and non-empty. - For
analyze: require at least one oflovable_url,lovable_code, ordescription. - For
build: require a prior spec (output of analyze) or adescriptionsufficient to build from. - For
refine: requirefeedback— reject without PM feedback input. - For
ship: require a prior build (output of build or refine).
Gate: All required fields present for the requested action.
Phase 2: Route to Pipeline
Determine which pipeline to invoke based on action:
| Action | Pipeline | Agents Involved |
|---|---|---|
analyze |
incubator-analyze |
spec-analyzer |
build |
incubator-build |
pit-builder, mobile-builder, quality-gate, reporter |
refine |
incubator-refine |
pit-builder, mobile-builder, quality-gate, reporter |
ship |
incubator-ship |
preview-generator, pit-builder (merge), reporter |
Prepare the input data payload for the target pipeline, passing through all relevant fields.
Phase 3: Trigger and Respond
Trigger the pipeline and return a structured response with the session ID.
Output Format
{
"pipeline": "incubator-build",
"session_id": "fleet-abc123",
"feature_name": "expense-tracker",
"status": "triggered",
"agents_involved": ["pit-builder", "mobile-builder", "quality-gate", "reporter"]
}
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 76 lines · 3 tokens per session scan A 596063ca0c13
orchestrate is a skill published in the GitHub repository srinidhis05/agentura (9 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 3 tokens to every session and 682 once invoked, about $0.0000 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.
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…