Cisco Engineer Wins AWS AI League: Nine Single-Variable Experiments Reveal That Every Agent Handoff Consumes Priced Output Tokens
Nishanth Aluhonnu, the 2026 AWS AI League champion, discovered through nine single-variable variants that tool return results and system prompts are not scored, but everything the agent writes—including tool call arguments—is counted. Based on this, he abandoned the reference architecture's supervisor-plus-sub-agent pattern in favor of a single-agent model with a dispatch table, moving routing logic into an AWS Lambda function, ultimately winning among 1,200 participants.
The 2026 AWS AI League hosted an agentic AI tournament at Cisco Transformation Fest 4.0, drawing 1,200 engineers. Champion Nishanth Aluhonnu’s design choices overturned a seemingly reasonable architectural convention: he defeated the competition’s reference architecture’s supervisor-plus-sub-agent pattern using a single agent.
Competition rules required agents to move across a grid map, solve various challenges (handling inappropriate content, running code, retrieving web information, extracting structured data), and reach a treasure chest. Scoring consisted of challenge points, treasure bonuses, remaining lives, and a token bonus calculated as 1,000 minus total output tokens divided by the number of visited challenges. This meant output tokens were a direct negative factor.
Aluhonnu built nine variants of the agent, changing only one factor at a time to isolate which tokens truly affected the score. The results were clear: tool return results and system prompts did not count against the score, but everything the agent wrote itself—including tool call arguments—was counted. Each tool call also carried approximately 52 fixed-overhead tokens.
This finding directly dictated architectural choices. The competition’s reference architecture showcased a supervisor agent coordinating three sub-agents (navigation, computation, web retrieval) routed to tools via AgentCore Gateway. Aluhonnu believed this pattern was reasonable for most production systems, but in this competition, every handoff between agents was a message the model had to write, and every written message consumed priced tokens. He switched to a single agent, placing a short dispatch table at the start of the prompt to map each challenge type to its corresponding method, completing routing within a single turn.