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 orchestrate-evaluatorgit 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-evaluator)<a href="https://agentmods.dev/skills/nitish-r-g/hackerrank-orchestrate-skills/orchestrate-evaluator"><img src="https://agentmods.dev/badge/skills/nitish-r-g/hackerrank-orchestrate-skills/orchestrate-evaluator/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-evaluator"><img src="https://agentmods.dev/badge/skills/nitish-r-g/hackerrank-orchestrate-skills/orchestrate-evaluator.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.00052 | $0.00807 |
| Opus 5 | $0.00026 | $0.00404 |
| Sonnet 5 | $0.00010 | $0.00161 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade A, and why
orchestrate-evaluator 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate: Orchestrate Evaluator
Evidence tier: first-hand build (August 2026). Grounded in a completed Orchestrate submission that was audited to destruction — 48 logged defects, 9 measured-and-rejected optimisations, 17 certification scripts. Every number below was measured on that system. Nothing here claims access to HackerRank's internal scoring.
What this answers
If I ship this today, what evidence says I am actually better?
Not "does the code look good."
The categories, and what a top submission looks like
| Category | Check | Strong signal |
|---|---|---|
| Specification | literal conformance to every clause | 0 violations, checked against transcribed constants |
| Evidence | cited ids exist, belong, don't self-reference | 0 hallucinated |
| Generalization | coupling probes, hardcoded ids | 0 ids in executable code; coupling probes pass |
| Determinism | processes × hash seeds | one hash, boundary stated |
| Security | injection, ReDoS, traversal, malformed media | every hostile input yields a valid row |
| Multimodal | counterfactual per modality | disabling the modality changes decisions |
| Release | fresh clone, artifact freshness, packaging | clone runs from README alone |
| Evaluation | output distribution sanity | no near-constant predictor |
Scoring rules that matter
Blockers cap everything. A score that lets fourteen passes outvote one release
blocker is worse than no score. Any blocker → DO NOT SHIP, regardless of the average.
Label your confidence. measured (a number was produced) / observed (read from
a file) / inferred (reasoning) / unknown. Discount inferred findings. Report
unknown; never guess it either way.
Evidence before score. Print blockers above the number. If a reader takes the score and ignores the findings, the report failed.
Distribution sanity — the cheap tell for a degenerate solution
- one action covering >80% of rows → a near-constant predictor can score well on an imbalanced set while learning nothing
- ≤2 distinct
message_typevalues → the type column is not being reasoned about - 1 distinct
reasonstring → a scored dimension is being wasted
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 · 71 lines · 52 tokens per session scan A 260cd2057446
orchestrate-evaluator is a skill published in the GitHub repository NITISH-R-G/hackerrank-orchestrate-skills (3 stars, last pushed 28d ago), licensed MIT. It adds 52 tokens to every session and 807 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-31.
Other skills, from other repositories
test-router
A testing skill that chooses which checks to run based on the type, scope, and risk of a change.
dev-testing
A testing guide that defines when to use unit, integration, API, and end-to-end tests. Unit tests check small pieces of code, while end-to-end tests check a full user flow.
release-verification
A release-verification checklist for software versions and packages. It covers changelogs, tests, packaging, installation smoke checks, version-control actions, publishing, and checks after release.
host-contract-verification
A verification procedure for the rules between a host system and its hooks, command-line tools, startup scripts, workspace checks, visible responses, and fallback connections to MCP servers.
api-verification
An API verification workflow that creates both an .http request file and a .cjs JavaScript file, then runs an automation script to test them. An API is an interface through which software exchanges requests and responses.
consumer-validation-engineering
A validation workflow for checking a software package across separate repositories. It covers SDKs, command-line tools, frameworks, and shared packages using both linked source code and the packaged artifact users install.