Borrowing it
Nothing to install: this file belongs to GregBaugues/tokenbowl-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/GregBaugues/tokenbowl-mcp/main/.claude/commands/waivers.mdgit clone --depth 1 https://github.com/GregBaugues/tokenbowl-mcpWrote 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/commands/gregbaugues/tokenbowl-mcp/waivers)<a href="https://agentmods.dev/commands/gregbaugues/tokenbowl-mcp/waivers"><img src="https://agentmods.dev/badge/commands/gregbaugues/tokenbowl-mcp/waivers/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/commands/gregbaugues/tokenbowl-mcp/waivers"><img src="https://agentmods.dev/badge/commands/gregbaugues/tokenbowl-mcp/waivers.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.00000 | $0.01309 |
| Opus 5 | $0.00000 | $0.00655 |
| Sonnet 5 | $0.00000 | $0.00262 |
| Haiku 4.5 | $0.00000 | $0.00131 |
Grade A, and why
waivers 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 9d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Waiver Wire Analysis
Analyze waiver wire opportunities for Bill Beliclaude (Roster ID 2) in the Token Bowl league.
Goal
Identify high-value waiver claims that improve our championship odds through:
- Roster need analysis (positions with critical depth gaps)
- Trending player identification (breakout candidates and league-winners)
- Recently dropped player evaluation (hidden gems from opponent mistakes)
- Defense streaming optimization (maximize weekly points)
- Strategic priority assessment (when to use waiver position)
Philosophy: Be aggressive with speculative adds that could win the championship. Better to miss on upside plays than miss playoffs holding mediocre players.
Execution Phases
Phase 1: Assess Team Needs
Use the roster-analyst subagent to identify positions of need:
- What positions have critical depth gaps (0-1 bench players)?
- Which positions face upcoming bye weeks?
- What are our weakest starting positions?
- Which players are droppable (declining value, excess depth)?
Reference: See .claude/reference/_fantasy_framework.md for roster construction priorities.
Key Framework:
- RB depth is critical (3-4 total, including speculative handcuffs)
- WR depth is important (4-6 total)
- QB/TE/K/DEF - minimal bench needs (can stream)
- Prioritize positions with 0-1 bench depth first
Untouchables: Josh Allen and James Cook are not droppable.
Phase 2: Identify Waiver Opportunities
Step 1: Get Consolidated Analysis
get_waiver_analysis(position=None, days_back=7, limit=20)
This returns recently dropped players AND trending available players in one efficient call.
Step 2: Expand Trending Analysis
get_trending_players(type="add", limit=25, position=None)
Focus on:
- Players with 20-100 adds (sweet spot for early adoption)
- Compare ROS projections to current scoring
- Identify breakout candidates before they fully break out
Step 3: Deep Dive on Top Candidates
For each serious candidate (top 10 from Steps 1-2):
search_players_by_name(name="Player Name")
Extract:
- ROS projections vs recent performance
- Bye week (critical - check if on bye THIS week)
- Depth chart position and role
- Injury status
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.
- 9d ago First seen · 162 lines · 0 tokens per session scan A 861cf1707fc6
waivers is a command published in the GitHub repository GregBaugues/tokenbowl-mcp (6 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,309 tokens. 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.