Borrowing it
Nothing to install: this file belongs to NITISH-R-G/hackerrank-orchestrate-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/NITISH-R-G/hackerrank-orchestrate-skills/master/AGENTS.mdgit 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/instructions/nitish-r-g/hackerrank-orchestrate-skills/agents-md)<a href="https://agentmods.dev/instructions/nitish-r-g/hackerrank-orchestrate-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/nitish-r-g/hackerrank-orchestrate-skills/agents-md/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/instructions/nitish-r-g/hackerrank-orchestrate-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/nitish-r-g/hackerrank-orchestrate-skills/agents-md.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.00546 | $0.00546 |
| Opus 5.5 | $0.00218 | $0.00218 |
| Sonnet 5.5 | $0.00109 | $0.00109 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
hackerrank-orchestrate-skills AGENTS.md 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - instructions for any AI coding agent
This repository holds Orchestrate skills: plain-markdown playbooks for the HackerRank Orchestrate hackathon, plus a Python toolkit that audits submissions.
Any agent can use them: Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Aider, or a plain chat model with the files pasted in. Skills are ordinary markdown. The SKILL.md frontmatter is only used by Claude Code's skill loader; every other agent reads the body text.
How to use the skills (any agent)
- Read
skills/INDEX.md. It maps each situation to one skill. - Start with
skills/orchestrate/SKILL.md. It holds the phase order and the failure routing. - Go to the phase skill it names. Each skill lists its
references/files. Read only the ones you need. - Re-open
orchestratewhenever a step fails.
Phase order: orchestrate -> orchestrate-build -> orchestrate-test-fix -> orchestrate-submit. orchestrate-interview runs in parallel from mid-build. orchestrate-reference is lookup only.
Rules for the agent working on a submission
- Never tune against sample rows until one number matches. That is overfitting.
- Model describes, code decides. Decisions use booleans and enums, never free text.
- Keep the output contract exact: column names, allowed values, separators, row count.
- Never write a number you did not measure. Use the provenance labels in
skills/orchestrate-interview/references/CONSTANTS-template.md. - Do not overwrite a starter
CLAUDE.mdorAGENTS.mdin the challenge repo. Append to it. - Keep a safe fallback output banked before any experiment.
- Before changing anything, state the metric it should move and the rows it could break.
Rules for working on this repository
- Python 3.10+. Run tests with
python -m pytest -q. - Tests must pass on Windows and Linux. Full git history is required for commit-provenance tests (
git fetch --unshallowon a shallow clone). - Keep skills in
skills/<name>/SKILL.mdwithnameanddescriptionfrontmatter. Keep each skill's detail inreferences/. - Do not add a new skill when an existing one covers the job. Edit the existing skill instead.
- Historical documents live in
docs/history/. Do not link to them from skills.
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 · 33 lines · 546 tokens per session scan A c7d00f8911fa
hackerrank-orchestrate-skills AGENTS.md is an instructions file published in the GitHub repository NITISH-R-G/hackerrank-orchestrate-skills (8 stars, last pushed 2d ago), licensed MIT. It adds 546 tokens to every session, about $0.0022 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.