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-agent-architecturegit 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-agent-architecture)<a href="https://agentmods.dev/skills/nitish-r-g/hackerrank-orchestrate-skills/orchestrate-agent-architecture"><img src="https://agentmods.dev/badge/skills/nitish-r-g/hackerrank-orchestrate-skills/orchestrate-agent-architecture/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-agent-architecture"><img src="https://agentmods.dev/badge/skills/nitish-r-g/hackerrank-orchestrate-skills/orchestrate-agent-architecture.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.00101 | $0.01814 |
| Opus 5 | $0.00051 | $0.00907 |
| Sonnet 5 | $0.00020 | $0.00363 |
| Haiku 4.5 | $0.00010 | $0.00181 |
Grade A, and why
orchestrate-agent-architecture 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate Agent Architecture
HackerRank's own description of the code rubric is unusually specific and worth quoting directly: it measures "whether submissions contain actual agent loops versus hardcoded workflows." That is a stated, explicit discriminator. It's also the single easiest place to lose 30% of your score while producing something that technically works.
The hardcoded-workflow trap
Under time pressure the tempting shape is:
for ticket in tickets:
category = classify(ticket) # one LLM call
if category == "billing":
urgency = check_billing_rules(ticket)
elif category == "technical":
urgency = check_tech_rules(ticket)
...
if urgency > THRESHOLD:
escalate(ticket)
else:
respond(ticket)
This can score well on raw correctness and still read as a decision tree with LLM calls embedded in it, not an agent. Every branch was decided by you, at authoring time. The model fills in blanks; it doesn't decide anything about how to approach the problem.
What an actual agent loop looks like
The distinguishing property: the model decides what to do next, and the loop continues until the model says it's done — rather than the control flow being fixed in advance by the author.
def run_agent(ticket, tools, max_steps=10):
messages = [system_prompt(), user_prompt(ticket)]
for step in range(max_steps):
response = model.call(messages, tools=tools)
if response.is_final_answer:
return response.answer
result = execute_tool(response.tool_call) # agent chose this tool
messages.append(response)
messages.append(result)
return fallback(messages) # hit step limit — handle explicitly
The agent chose: which tool, with which arguments, how many times, and when to stop. That's the thing being scored.
This is not an argument for maximum autonomy. A loop that wanders for 40 steps is worse than a tight pipeline. The point is that the structure should let the model make decisions where judgment is genuinely required, with bounded steps and explicit fallbacks — not that you should remove all structure.
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 · 102 lines · 101 tokens per session scan A f6e9a5d99c3d
orchestrate-agent-architecture is a skill published in the GitHub repository NITISH-R-G/hackerrank-orchestrate-skills (3 stars, last pushed 29d ago), licensed MIT. It adds 101 tokens to every session and 1,814 once invoked, about $0.0005 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.