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/natea/exomind/challengesgit clone --depth 1 https://github.com/natea/ExoMindWhat 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.00014 | $0.00667 |
| Opus 5 | $0.00007 | $0.00333 |
| Sonnet 5 | $0.00003 | $0.00133 |
| Haiku 4.5 | $0.00001 | $0.00067 |
Grade A, and why
flow-nexus-challenges 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 2d 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.
This is a copy
100% identical to flow-nexus-challenges — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flow Nexus Challenges
Complete coding challenges to earn rUv credits and climb the leaderboard.
List Challenges
mcp__flow-nexus__challenges_list({
difficulty: "intermediate", // beginner, advanced, expert
category: "algorithms",
status: "active",
limit: 20
})
Get Challenge Details
mcp__flow-nexus__challenge_get({
challenge_id: "two-sum-problem"
})
Submit Solution
mcp__flow-nexus__challenge_submit({
challenge_id: "challenge_id",
user_id: "your_id",
solution_code: `
function solution(nums, target) {
const map = new Map();
for (let i = 0; i < nums.length; i++) {
const complement = target - nums[i];
if (map.has(complement)) {
return [map.get(complement), i];
}
map.set(nums[i], i);
}
return [];
}
`,
language: "javascript",
execution_time: 45 // milliseconds
})
Complete Challenge
mcp__flow-nexus__app_store_complete_challenge({
challenge_id: "challenge_id",
user_id: "your_id",
submission_data: {
passed_tests: 10,
total_tests: 10,
execution_time: 45
}
})
Leaderboards
// Global leaderboard
mcp__flow-nexus__leaderboard_get({
type: "global", // weekly, monthly, challenge
limit: 10
})
// Challenge-specific leaderboard
mcp__flow-nexus__leaderboard_get({
type: "challenge",
challenge_id: "specific_challenge",
limit: 25
})
Achievements
mcp__flow-nexus__achievements_list({
user_id: "your_id",
category: "speed_demon" // Categories vary
})
rUv Credits
// Check balance
mcp__flow-nexus__ruv_balance({ user_id: "your_id" })
// View history
mcp__flow-nexus__ruv_history({
user_id: "your_id",
limit: 20
})
// Earn credits (automatic on completion)
mcp__flow-nexus__app_store_earn_ruv({
user_id: "your_id",
amount: 100,
reason: "Completed expert challenge",
source: "challenge"
})
Challenge Categories
- algorithms: Classic algorithm problems
- data-structures: DS implementation challenges
- system-design: Architecture challenges
- optimization: Performance challenges
- security: Security-focused problems
- ml-basics: Machine learning fundamentals
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.
- 2d ago First seen · 120 lines · 14 tokens per session scan A 5ab45467885d
flow-nexus-challenges is a command published in the GitHub repository natea/ExoMind (21 stars, last pushed 10mo ago), licensed MIT. It adds 14 tokens to every session and 667 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to flow-nexus-challenges, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.