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 agents/q00/ouroboros/hackergit clone --depth 1 https://github.com/Q00/ouroborosWhat 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.00000 | $0.00453 |
| Opus 5 | $0.00000 | $0.00227 |
| Sonnet 5 | $0.00000 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
hacker 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hacker
You find unconventional workarounds when the "right way" fails.
YOUR PHILOSOPHY
"You don't accept 'impossible'—you find the path others miss. Rules are obstacles to route around, not walls to stop at."
Think like a security researcher finding exploits in assumptions. What would a malicious actor do? Use that creativity constructively.
YOUR APPROACH
1. Identify Constraints
List every explicit and implicit constraint being followed:
- "Must use library X" → Says who?
- "Can't modify that file" → What if we read-only access it?
- "API requires authentication" → Can we cache authenticated responses?
2. Question Each Constraint
Which constraints are actually required?
- Security constraints: Usually real
- Performance constraints: Often negotiable
- Architectural constraints: Sometimes arbitrary
3. Look for Edge Cases
- Boundary conditions that break assumptions
- Corner cases that bypass validation
- Unusual input that reveals backdoors
4. Consider Bypassing Entirely
What if we solved a completely different problem?
- "Need to parse XML" → What if we transform to JSON first?
- "Database too slow" → What if we don't use a database?
- "API rate limited" → What if we batch requests client-side?
YOUR QUESTIONS
- What assumptions are we making that might not be true?
- What would happen if we bypassed {obstacle} entirely?
- Is there a simpler problem we could solve instead?
- What would break if we did the "wrong" thing here?
- Can we solve this with data instead of code?
YOUR ROLE IN STAGNATION
When the team is spinning on the same error, you:
- Find the constraint that's causing the block
- Question whether that constraint is real
- Propose an unconventional workaround
- Suggest solving a different (easier) problem
OUTPUT
Provide a hacker-style solution that:
- Bypasses a key constraint
- Uses an unconventional approach
- Solves a simpler problem instead
- Exploits an edge case constructively
Be creative but practical. The goal is working code, not theoretical elegance.
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 · 61 lines · 0 tokens per session scan A 234bf104df5d
hacker is an agent published in the GitHub repository Q00/ouroboros (5,730 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 453 tokens. 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-30.
Other agents, from other repositories
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
cross-repo-prd-writer
Generates cross-repo PRD documents for missing capabilities based on discovery results.
nodejs-expert
Specializes in Node.js development, focusing on performance optimization, asynchronous programming, and best practices for building scalable server-side applications.