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 anton-abyzov/vskill --skill tournament-managergit clone --depth 1 https://github.com/anton-abyzov/vskillWrote 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/anton-abyzov/vskill/tournament-manager)<a href="https://agentmods.dev/skills/anton-abyzov/vskill/tournament-manager"><img src="https://agentmods.dev/badge/skills/anton-abyzov/vskill/tournament-manager/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/anton-abyzov/vskill/tournament-manager"><img src="https://agentmods.dev/badge/skills/anton-abyzov/vskill/tournament-manager.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.00188 | $0.01195 |
| Opus 5 | $0.00094 | $0.00598 |
| Sonnet 5 | $0.00038 | $0.00239 |
| Haiku 4.5 | $0.00019 | $0.00120 |
Grade A, and why
tournament-manager 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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tournament Manager (EasyChamp)
Run tournaments end-to-end without leaving Claude — generate a league, spin up a tournament under it, build the bracket, create the schedule, and enter results as matches finish. Powered by the EasyChamp MCP running over stdio.
When to Use
- A league needs to be created ("Start the summer basketball league, 8 teams, single-elim").
- A tournament needs to be spun up under an existing league.
- A bracket must be generated from a tournament's team list.
- A match schedule must be produced with optional venue assignments.
- A match result must be recorded against the bracket.
Chain order is usually: easychamp_generate_league → easychamp_generate_tournament → easychamp_generate_bracket → easychamp_create_schedule → easychamp_enter_results (one per match).
MCP Tools
All tools live on the EasyChamp MCP server. Invoke them as-is; the server is configured via the Deps tab snippet (see below).
easychamp_generate_league
Create a new league under the authenticated organization.
Input:
{
"name": "Summer Basketball League",
"sport": "basketball",
"teamCount": 8,
"format": "single_elim"
}
Output: { leagueId, name, sport, teams: string[] }.
easychamp_generate_tournament
Create a tournament inside an existing league.
Input: { "leagueId": "lg_abc123", "type": "single_elim" }
Output: { tournamentId, leagueId, type }.
easychamp_generate_bracket
Build the bracket for a tournament from its registered teams.
Input: { "tournamentId": "tn_xyz789" }
Output: { bracketId, rounds: Match[] }.
easychamp_create_schedule
Produce the schedule with match dates (and optional venues).
Input:
{
"tournamentId": "tn_xyz789",
"startDate": "2026-06-01",
"venues": ["Court A", "Court B"]
}
Output: { scheduleId, matches: ScheduledMatch[] }.
easychamp_enter_results
Record the final score + winner for a single match.
Input: { "matchId": "m_42", "homeScore": 84, "awayScore": 77, "winner": "home" }
Output: { matchId, finalized: true }.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +95 lines · +163 tokens per session b184e86c3618
- 10d ago First seen · 17 lines · 25 tokens per session scan A 5d7eae287eaf
tournament-manager is a skill published in the GitHub repository anton-abyzov/vskill (45 stars, last pushed 2d ago), licensed MIT. It adds 188 tokens to every session and 1,195 once invoked, about $0.0009 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
help-flow
Help about Rosetta: explains capabilities and usage.
external-lib-flow
Workflow for onboarding an external private library so AI can use it without source access.
modernization-flow
Workflow for converting, modernizing, upgrading, or re-architecting code (e.g. C++→Java, monolith→microservices), etc.
Agent Browser Automation
Fast Rust-based headless browser automation CLI with Node.js fallback for AI agents, featuring navigation, clicking, typing, snapshots, and structured commands optimized for agent workflows.
coding-flow
Light coding workflow: features, fixes, refactors, unit tests, etc.; scales small to large.
adhoc-flow
Workflow for the rest of tasks: lightweight documentation, build, track, synchronize, etc.