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 NITISH-R-G/hackerrank-orchestrate-skills --skill orchestrategit clone --depth 1 https://github.com/NITISH-R-G/hackerrank-orchestrate-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/nitish-r-g/hackerrank-orchestrate-skills/orchestrate)<a href="https://agentmods.dev/skills/nitish-r-g/hackerrank-orchestrate-skills/orchestrate"><img src="https://agentmods.dev/badge/skills/nitish-r-g/hackerrank-orchestrate-skills/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/nitish-r-g/hackerrank-orchestrate-skills/orchestrate"><img src="https://agentmods.dev/badge/skills/nitish-r-g/hackerrank-orchestrate-skills/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.00077 | $0.01682 |
| Opus 5.5 | $0.00031 | $0.00673 |
| Sonnet 5.5 | $0.00015 | $0.00336 |
| Haiku 4.5 | $0.00008 | $0.00168 |
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 yesterday.
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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate: Master Plan
Goal: maximise the final score in every section. Final = 0.30 Code + 0.30 Output CSV + 0.30 AI Interview + 0.10 Transcript. Ties break in the order Interview, Code, Output CSV, Transcript.
Balance wins. Past winners were strong in all four. A huge score in one section does not carry the rank.
The six skills and when to use each
| Skill | Use it when | Ends when |
|---|---|---|
orchestrate (this) |
Start, lost, or anything failed | You know the next skill |
orchestrate-build |
Problem statement and sample data are read | Pipeline runs end to end on sample, DESIGN.md written |
orchestrate-test-fix |
Pipeline runs on sample | Wrong rows are classified and fixed, output is stable |
orchestrate-submit |
Output is stable | Self-score done, hardening done, packaging checked |
orchestrate-interview |
Output is stable (start prep earlier) | You can defend every number and decision |
orchestrate-package |
Output is final. Check submission readiness against the statement and build submission/ |
— |
orchestrate-score |
Before submit, or to pick the next fix. Estimated score with published weights | — |
orchestrate-reference |
You need a ready-to-paste prompt, a principle, a checklist, or past-winner patterns | Never. Read on demand |
Order: this -> build -> test-fix -> submit (with interview prep running in parallel from hour 14) -> final freeze.
Clock for 24 hours (adjust once the problem is known)
| Hours | Do | Skill |
|---|---|---|
| 0-1 | Read problem statement, sample data, rubric. Write output contract | orchestrate, build |
| 1-3 | DESIGN.md, decision rules, escalation rules, failure table | build |
| 3-8 | Build pipeline. Run on sample. First CSV | build |
| 8-14 | Test edge cases and overfitting. Fix wrong rows in one-change loops | test-fix |
| 14-17 | Review every justification. Second strategy comparison | test-fix |
| 17-19 | Self-score, security pass, cost numbers | submit |
| 14-20 | Interview prep in parallel: CONSTANTS.md, nine topics, rehearsal | interview |
| 21-23 | Clean run from empty folder, spec audit, release checklist | submit |
| 23-24 | Buffer. No new features | - |
What ships with it
4 files 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.
- yesterday First seen · 115 lines · 77 tokens per session scan A 701e6a82a40a
orchestrate is a skill published in the GitHub repository NITISH-R-G/hackerrank-orchestrate-skills (8 stars, last pushed 2d ago), licensed MIT. It adds 77 tokens to every session and 1,682 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-10-24.
Other skills, from other repositories
product-strategy
A product-planning guide for evaluating requirements, users, scope, priorities, roadmaps, and success measures. It ties proposals to user problems, business value, boundaries, and signals that can be checked.
project-inception
Use when kicking off a new project or feature area in an ocul-pm tracked project (.oculpm/ present) — research the stack landscape via web search, then converse with the user (research-backed choices) to settle the optimal spec, and seed a discussion doc, a detailed 3-depth plan (plancreate), EVALS.md done-criteria…
help
A reference guide to the ocul-pm commands, tools, skills, and automatic hooks. Hooks are automatic actions triggered by events such as starting or ending a session.
next
A planned implementation loop that selects the next unfinished task, implements it, checks the result, records a work note, and updates the plan.
project_init
A project setup command that initializes a repository for ocul-pm tracking by creating its planning and journal structure, recording rules, and protected ignore-file entries.
standup
A stand-up report generator that combines the day's work notes with the current project plan. A stand-up is a short progress update covering completed work, blockers, and next steps.