Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/NITISH-R-G/hackerrank-orchestrate-skillsnpx agentmods add skills/nitish-r-g/hackerrank-orchestrate-skills/orchestrate-submission-validatorWrote 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-submission-validator)<a href="https://agentmods.dev/skills/nitish-r-g/hackerrank-orchestrate-skills/orchestrate-submission-validator"><img src="https://agentmods.dev/badge/skills/nitish-r-g/hackerrank-orchestrate-skills/orchestrate-submission-validator/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-submission-validator"><img src="https://agentmods.dev/badge/skills/nitish-r-g/hackerrank-orchestrate-skills/orchestrate-submission-validator.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.00055 | $0.00545 |
| Opus 5 | $0.00028 | $0.00272 |
| Sonnet 5 | $0.00011 | $0.00109 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade A, and why
orchestrate-submission-validator 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 10d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate: Submission Validator
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.
The rule
Any generated artifact is stale until proven current, in the same breath as the code that generates it.
What this caught in a real build
output.csv was 28 rows different from what the committed code produced. It had
been generated three commits earlier. Nothing in a file listing shows this — the file
exists, has a sane size, and opens fine.
Found by regenerating to a temp path and comparing hashes. Never by looking at it.
The procedure
# 1. Regenerate to a TEMP path -- never overwrite the artifact you are checking
python code/main.py --out /tmp/regen.csv
# 2. Hash both
sha256sum dataset/output.csv /tmp/regen.csv
# 3. Identical? current. Different? stale -- regenerate before shipping.
If your entry point has no --out flag, add one. A pipeline that can only write
to one hardcoded path cannot be verified without destroying the thing being verified.
The checklist
-
git status --porcelainempty for tracked files - Artifact regenerated to a temp path and hash-compared
- The artifact was produced by the current commit
- Package rebuilt after the last code change, not before
- Every file in the package byte-matches the working tree
- No
__pycache__, caches, or editor files in the package - No secrets in the package, the repo, or git history
- Transcript artifact located and current
Failure modes
- Rebuilding the package before the final commit. Order matters: code → artifact → package.
- Trusting a timestamp. A file touched by an unrelated tool looks fresh.
- Checking the working tree but not history for secrets. A rotated key is still in history unless purged.
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.
- 10d ago First seen · 55 lines · 55 tokens per session scan A 9c705cc59da5
orchestrate-submission-validator is a skill published in the GitHub repository NITISH-R-G/hackerrank-orchestrate-skills (3 stars, last pushed 29d ago), licensed MIT. It adds 55 tokens to every session and 545 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
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.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
Changelog Test Mapper
Map changelog entries and release notes to affected test cases, ensuring every user-facing change has corresponding test coverage verification.
AI Release Guardian
Analyze a git diff, map affected risks, select the tests that matter, detect coverage gaps on changed lines, run configurable quality gates, and produce a go/no-go release report with cited evidence. Recommends only; never merges or deploys.