Software for HackerRank Orchestrate: an evaluator, an engineering-memory CLI that remembers what you measured and rejected, a mentor that costs a change before you write it, an adaptive AI-judge interview simulator, and 34 auto-triggering Agent Skills.
Run the final release gate: fresh-clone simulation, artifact freshness, packaging hygiene, documentation accuracy. Use in the final hour. Catches the defects that make a working submission fail on someone else's machine.
Defending an LLM agent against adversarial input — prompt injection, jailbreak attempts, ambiguous edge cases, and malformed model output — as an explicit design phase rather than a bug-fixing afterthought. Use when building any agent that processes untrusted or user-supplied input, when a challenge dataset is…
Design a deterministic routing engine that is auditable and injection-immune. Use when choosing between rules and an LLM classifier, and when ordering rule tiers. Includes how to prove no rule is dead or shadowed.
Build validation guardrails around every LLM-generated field before it reaches output.csv in a HackerRank Orchestrate submission — schema validation, rejecting unsupported label values, and retry-on-malformed-output. Use this whenever writing the code path that turns a model response into a CSV row, when an agent's…
Attack your own submission across injection, unicode evasion, regex denial of service, path traversal, and malformed media. Use before release. Every failure path must degrade to a valid output rather than crash.
Honestly estimating how a HackerRank Orchestrate submission (or similar multi-signal AI evaluation) would score across every rubric dimension before submitting, to find the weakest area while there's still time to fix it. Use before final submission of any Orchestrate-style challenge, or whenever the user asks "how…
Verify a submission against the literal text of problemstatement.md rather than your memory of it — every column, every allowed value, every separator, every required artifact. Use before any release, and immediately after any change to output formatting. Catches the class of defect that costs points mechanically…
Final pre-submission checklist for a HackerRank Orchestrate (or similar multi-artifact hackathon) submission — packaging, file format compliance, and the mechanical failure modes that lose points for reasons unrelated to your agent's quality. Use in the final phase before submitting, or whenever the user asks to do a…
Prove the three submission artifacts are current, consistent, and correspond to the same commit. Use in the final hour, and after any change that touches production code. Catches stale outputs, which is the single most common silent submission defect.
Score a chat transcript against HackerRank's published AI Chat Transcript rubric, and generate prompts that demonstrate the behaviors it rewards -- direction/ownership, technical specificity, iteration/verification, safety awareness. Use before submitting, or at the start of a build to prompt yourself better from turn…
★not rated 3 1mo agoA65 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: