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 skills add proffesor-for-testing/agentic-qe --skill agent-challengesgit clone --depth 1 https://github.com/proffesor-for-testing/agentic-qeWrote 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/proffesor-for-testing/agentic-qe/agent-challenges)<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/agent-challenges"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/agent-challenges/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/agent-challenges"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/agent-challenges.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00015 | $0.00743 |
| Opus 5.5 | $0.00006 | $0.00297 |
| Sonnet 5.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 1mo 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 agent-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.
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.
- 1mo ago First seen · 86 lines · 15 tokens per session scan A 2fc8d705facf
agent-challenges is a skill published in the GitHub repository proffesor-for-testing/agentic-qe (506 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.5. A static security scan graded it A with 0 findings. It is 100% identical to agent-challenges, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…