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 agentmods add instructions/dubsopenhub/havoc-hackathon/agents-mdgit clone --depth 1 https://github.com/DUBSOpenHub/havoc-hackathonWrote 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/dubsopenhub/havoc-hackathon/agents-md)<a href="https://agentmods.dev/instructions/dubsopenhub/havoc-hackathon/agents-md"><img src="https://agentmods.dev/badge/instructions/dubsopenhub/havoc-hackathon/agents-md.svg" alt="Measured on agentmods" 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 | $0.00677 | $0.00677 |
| Opus 5 | $0.00338 | $0.00338 |
| Sonnet 5 | $0.00135 | $0.00135 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
havoc-hackathon AGENTS.md scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sL https://raw.githubusercontent.com/DUBSOpenHub/havoc-hackathon/main/skills/havoc-hackathon/SKILL.md \ How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agents
Overview
Havoc Hackathon ships two Copilot CLI agents and one skill. The skill (havoc-hackathon) is the primary entry point — it orchestrates full multi-model tournaments. The havoc-hackathon agent is a standalone agent version of the same capability. The grid-medic agent is bundled as a companion for keeping the tournament infrastructure healthy.
Available Agents
havoc-hackathon (Skill)
- Purpose: Multi-model AI tournament orchestrator. Dispatches up to 13 current full-size AI models in elimination heats, scores them with sealed judge panels (judges never know which model wrote what), evolves the best ideas between rounds, synthesizes a final output from all finalists, and maintains persistent ELO ratings across sessions.
- Usage: Install via Copilot CLI, then invoke with natural language:
run hackathon # Full tournament on whatever you describe run hackathon express # Quick single-round version /skills add DUBSOpenHub/havoc-hackathon # Instant install - Model: Dispatches to all available models in your Copilot CLI session
- Install:
mkdir -p ~/.copilot/skills/havoc-hackathon ~/.copilot/agents && \ curl -sL https://raw.githubusercontent.com/DUBSOpenHub/havoc-hackathon/main/skills/havoc-hackathon/SKILL.md \ -o ~/.copilot/skills/havoc-hackathon/SKILL.md - Location:
skills/havoc-hackathon/SKILL.md
havoc-hackathon (Agent)
- Purpose: Standalone agent version of the tournament orchestrator. Use when you want the Havoc Hackathon capability as a named agent rather than a skill.
- Usage: After installing
~/.copilot/agents/havoc-hackathon.agent.md, invoke via the agent selector in Copilot CLI. - Location:
agents/havoc-hackathon.agent.md
grid-medic
- Purpose: Companion agent bundled with Havoc Hackathon. Self-healing meta-agent that monitors and repairs the
.agent.mdfiles in your fleet — including Havoc Hackathon's own agent files. See DUBSOpenHub/grid-medic for full documentation. - Usage:
grid-medic diagnose grid-medic improve havoc-hackathon - Location:
agents/grid-medic.agent.md
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.
- 4d ago First seen · 51 lines · 677 tokens per session scan A c18aa0ceb2bc
havoc-hackathon AGENTS.md is an instructions file published in the GitHub repository DUBSOpenHub/havoc-hackathon (5 stars, last pushed 1mo ago), licensed MIT. It adds 677 tokens to every session, about $0.0034 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
dark-factory AGENTS.md
Instructions for DUBSOpenHub/dark-factory, covering agents.md — working guide for ai agents, architecture, file ownership map, before you change anything and agent prompt rules.
dark-factory copilot-instructions.md
Instructions for DUBSOpenHub/dark-factory, covering copilot instructions — dark factory, file map, non-negotiables, prohibited actions and pr requirements.
strategos AGENTS.md
AGENTS.md instructions for BigBugaboo/strategos, covering strategos contributor guidance, mission, commands, engineering rules and definition of done.
strategos CLAUDE.md
Claude Code instructions for BigBugaboo/strategos: Read and follow AGENTS.md before making changes. Keep edits scoped to the assigned task and do not merge, push, or remove worktrees unless explicitly requested.
strategos copilot-instructions.md
Copilot instructions for BigBugaboo/strategos, a project described as: Local-first strategist for Claude Code, Codex CLI, and GitHub Copilot CLI.
all-agents-mcp CLAUDE.md
Instructions for Dokkabei97/all-agents-mcp, covering claude.md, project overview, build & development commands, architecture and entry flow.