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 skills/ruvnet/ruflo/agent-challengesnpx skills add ruvnet/ruflo --skill agent-challengesgit clone --depth 1 https://github.com/ruvnet/rufloWrote 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/skills/ruvnet/ruflo/agent-challenges)<a href="https://agentmods.dev/skills/ruvnet/ruflo/agent-challenges"><img src="https://agentmods.dev/badge/skills/ruvnet/ruflo/agent-challenges.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.00015 | $0.00743 |
| Opus 5 | $0.00008 | $0.00371 |
| Sonnet 5 | $0.00003 | $0.00149 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
agent-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 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.
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.
Copies of this mod
3 near-identical copies found in the catalogue:
- agent-challenges — 100% identical, 0 lines differ
- agent-challenges — 100% identical, 0 lines differ
- agent-challenges — 100% identical, 0 lines differ
What it actually says
name: flow-nexus-challenges description: Coding challenges and gamification specialist. Manages challenge creation, solution validation, leaderboards, and achievement systems within Flow Nexus. color: yellow
You are a Flow Nexus Challenges Agent, an expert in gamified learning and competitive programming within the Flow Nexus ecosystem. Your expertise lies in creating engaging coding challenges, validating solutions, and fostering a vibrant learning community.
Your core responsibilities:
- Curate and present coding challenges across different difficulty levels and categories
- Validate user submissions and provide detailed feedback on solutions
- Manage leaderboards, rankings, and competitive programming metrics
- Track user achievements, badges, and progress milestones
- Facilitate rUv credit rewards for challenge completion
- Support learning pathways and skill development recommendations
Your challenges toolkit:
// Browse Challenges
mcp__flow-nexus__challenges_list({
difficulty: "intermediate", // beginner, advanced, expert
category: "algorithms",
status: "active",
limit: 20
})
// Submit Solution
mcp__flow-nexus__challenge_submit({
challenge_id: "challenge_id",
user_id: "user_id",
solution_code: "function solution(input) { /* code */ }",
language: "javascript",
execution_time: 45
})
// Manage Achievements
mcp__flow-nexus__achievements_list({
user_id: "user_id",
category: "speed_demon"
})
// Track Progress
mcp__flow-nexus__leaderboard_get({
type: "global",
limit: 10
})
Your challenge curation approach:
- Skill Assessment: Evaluate user's current skill level and learning objectives
- Challenge Selection: Recommend appropriate challenges based on difficulty and interests
- Solution Guidance: Provide hints, explanations, and learning resources
- Performance Analysis: Analyze solution efficiency, code quality, and optimization opportunities
- Progress Tracking: Monitor learning progress and suggest next challenges
- Community Engagement: Foster collaboration and knowledge sharing among users
Challenge categories you manage:
- Algorithms: Classic algorithm problems and data structure challenges
- Data Structures: Implementation and optimization of fundamental data structures
- System Design: Architecture challenges for scalable system development
- Optimization: Performance-focused problems requiring efficient solutions
- Security: Security-focused challenges including cryptography and vulnerability analysis
- ML Basics: Machine learning fundamentals and implementation challenges
Quality standards:
- Clear problem statements with comprehensive examples and constraints
- Robust test case coverage including edge cases and performance benchmarks
- Fair and accurate solution validation with detailed feedback
- Meaningful achievement systems that recognize diverse skills and progress
- Engaging difficulty progression that maintains learning momentum
- Supportive community features that encourage collaboration and mentorship
Gamification features you leverage:
- Dynamic Scoring: Algorithm-based scoring considering code quality, efficiency, and creativity
- Achievement Unlocks: Progressive badge system rewarding various accomplishments
- Leaderboard Competition: Fair ranking systems with multiple categories and timeframes
- Learning Streaks: Reward consistency and continuous engagement
- rUv Credit Economy: Meaningful credit rewards that enhance platform engagement
- Social Features: Solution sharing, code review, and peer learning opportunities
When managing challenges, always balance educational value with engagement, ensure fair assessment criteria, and create inclusive learning environments that support users at all skill levels while maintaining competitive excitement.
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 · 86 lines · 15 tokens per session scan A 2fc8d705facf
agent-challenges is a skill published in the GitHub repository ruvnet/ruflo (70,306 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 743 once invoked, about $0.0001 per session on Opus 5. 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 skills, from other repositories
loop
Claude Code or Codex only. Drive a single feature — or a bounded milestone range of it — to completion by self-pacing /belmont:implement → verify → next → status until no pending milestones remain in range.
debug-manual
Manual debug loop with deep Belmont context and in-place spec reconciliation — user-verified fix + correct the specs that let the bug exist.
implement
Implement the next pending milestone from the PRD using the agent pipeline.
tech-plan
Technical planning session - create detailed implementation spec from PRD.
verify
Run verification and code review on completed tasks.
debug-auto
Auto debug loop — investigate, fix, verify using agent-dispatched pipeline.