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 commands/wingedguardian/genesis-agi/challengegit clone --depth 1 https://github.com/WingedGuardian/GENesis-AGIWrote 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/commands/wingedguardian/genesis-agi/challenge)<a href="https://agentmods.dev/commands/wingedguardian/genesis-agi/challenge"><img src="https://agentmods.dev/badge/commands/wingedguardian/genesis-agi/challenge.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.00000 | $0.00104 |
| Opus 5 | $0.00000 | $0.00052 |
| Sonnet 5 | $0.00000 | $0.00021 |
| Haiku 4.5 | $0.00000 | $0.00010 |
Grade A, and why
challenge 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 5d 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.
What it actually says
Read the specified design doc section.
Identify:
- The 3 weakest assumptions in this design
- What breaks first in production under load?
- Most likely edge case discovered during implementation?
- What dependency change would invalidate this design?
- Strongest argument AGAINST implementing this?
Rate each finding:
- Likelihood: high / medium / low
- Impact if it occurs: high / medium / low
- Mitigation cost: trivial / moderate / expensive
Output as a structured risk assessment.
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.
- 5d ago First seen · 16 lines · 0 tokens per session scan A f4ca2605ef15
challenge is a command published in the GitHub repository WingedGuardian/GENesis-AGI (93 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 104 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 commands, from other repositories
review-prs
Check open PRs for human feedback before picking new work.
brief-refresh
Audit docs for staleness and contradictions, propose new features.
next-issue
Fetch the next ready-for-agent issue by priority.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.