Cisco Engineer Wins AWS AI League: Nine Single-Variable Experiments Reveal That Every Agent Handoff Consumes Priced Output Tokens
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.
The second design decision was moving deterministic logic into tools. Route planning was not left to the model but ran in an AWS Lambda function, treating the board as an optimization problem: each tile had an expected value equal to the points it paid minus potential life costs minus the tokens the agent would spend solving it. The planner respected constraints (such as collecting keys before opening doors) and optimized routes within a time budget.
This principle received dramatic validation in the second round of the finals. A seven-by-seven board was almost entirely covered with coins worth 25 points each, while a scheduling challenge tile was worth 1,500 points. The habitual reaction was to collect coins, but the planner’s value table deemed them noise. The agent went straight for the high-value challenge, scoring 7,537 in that round, nearly 1,600 points higher than the next finalist’s 5,953. The lead established in this round ultimately secured the overall championship.
During the qualifier stage, the top four agents all solved the map. The first-place agent output 1,220 tokens, the second-place agent output 1,430, and the final margin was only 16 points out of a total score near 16,000. When all agents can complete the task, efficiency determines the winner. The article thus distilled a migration principle: let models handle language and judgment, and move search, mathematics, and rules into tools because they are faster, cheaper, and more repeatable.
Sources:Amazon Web Services