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-submission-reviewgit 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-submission-review)<a href="https://agentmods.dev/skills/nitish-r-g/hackerrank-orchestrate-skills/orchestrate-submission-review"><img src="https://agentmods.dev/badge/skills/nitish-r-g/hackerrank-orchestrate-skills/orchestrate-submission-review/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-review"><img src="https://agentmods.dev/badge/skills/nitish-r-g/hackerrank-orchestrate-skills/orchestrate-submission-review.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.00079 | $0.00921 |
| Opus 5 | $0.00039 | $0.00461 |
| Sonnet 5 | $0.00016 | $0.00184 |
| Haiku 4.5 | $0.00008 | $0.00092 |
Grade A, and why
orchestrate-submission-review 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 12d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate Submission Review
This is the last gate, and it exists because a meaningful fraction of lost points in any timeboxed contest are mechanical, not intellectual — a malformed CSV, a missing file, a zip with the wrong structure, a README that doesn't explain how to run the thing. None of that reflects your agent's quality, and all of it is 100% preventable with a checklist run at a fixed point before the deadline, not "whenever there's time."
Do this with time to spare, not at the deadline
Run this pass at least 45–60 minutes before the actual deadline. Submission portals fail, uploads time out, and a discovered problem at T-minus-10-minutes is a crisis; the same problem at T-minus-60 is a fix.
Mechanical checks
The code zip:
- Does it actually contain everything needed to run the agent, or does it reference local files/paths that only exist on your machine?
- Does a fresh clone/extract + the documented setup steps actually work? (Test this literally — don't assume.)
- Are secrets/API keys excluded, and is there a clear
.env.exampleor equivalent instead of a hardcoded key? - Is there a README, and does it explain design decisions, not just run commands? (See
orchestrate-agent-architecture— this is scored, not cosmetic.) - Is the zip structured the way the submission instructions ask, or did you guess?
The output CSV:
- Does it parse cleanly with a standard CSV reader — no broken quoting, no stray delimiters from unescaped commas in justification text?
- Does the column structure match exactly what was specified (names, order, types)?
- Does every row have a value in every required column — no silent nulls from an unhandled exception mid-run?
- Row count: does it match the number of input tickets? A missing row is worse than a wrong row — it's not partial credit, it's an obvious gap.
- Re-run the full pipeline once, end to end, from a clean state, and diff the output against what you're about to submit. Catches stale/cached output being submitted by accident — a real and common failure.
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.
- 12d ago First seen · 52 lines · 79 tokens per session scan A 775c47abbe2f
orchestrate-submission-review is a skill published in the GitHub repository NITISH-R-G/hackerrank-orchestrate-skills (3 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 921 once invoked, about $0.0004 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
general
Handle everyday conversation, answer questions, manage files, take notes, run scripts, and maintain persistent memory across sessions. Use when the user asks a general question, requests file operations, wants to brainstorm ideas, needs to-do tracking, asks you to remember something, or requests skill search and…
multi-bot
Coordinates responses between multiple GolemBot instances in a shared fleet. Use when the bot operates in a group chat with other bots, needs to decide whether to respond or pass, or must call a peer bot's API to fetch cross-domain data.
kb-guide
Search, read, create, and update knowledge base entries via MCP-connected KB tools. Use when the user asks to look up documentation, find existing articles, check if docs exist on a topic, create a new KB entry, update an existing document, or when domain questions should be answered from the knowledge base first.
ops
Content operations assistant — drafts blog posts, social media copy, and marketing materials, compiles data briefings, and tracks competitor activity. Use when the user asks to write a blog post, draft social media content, create marketing copy, generate a weekly report, compile operational metrics, update the…
escalation
Escalate unresolvable or sensitive requests to a human agent by recording an escalation entry. Use when the user asks to speak to a human, the bot cannot answer confidently, the request involves financial, legal, or security concerns, a safety issue is detected, or the user is frustrated after repeated failures.
code-review
Reviews code changes, pull requests, and diffs for correctness, security, performance, and style. Use when the user submits a PR for review, asks to review a diff or code snippet, or requests a quality check on recent changes.