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 derekrbreese/fantasy-football-skills --skill faab-biddinggit clone --depth 1 https://github.com/derekrbreese/fantasy-football-skillsWrote 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/derekrbreese/fantasy-football-skills/faab-bidding)<a href="https://agentmods.dev/skills/derekrbreese/fantasy-football-skills/faab-bidding"><img src="https://agentmods.dev/badge/skills/derekrbreese/fantasy-football-skills/faab-bidding/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/derekrbreese/fantasy-football-skills/faab-bidding"><img src="https://agentmods.dev/badge/skills/derekrbreese/fantasy-football-skills/faab-bidding.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.00127 | $0.02827 |
| Opus 5 | $0.00063 | $0.01413 |
| Sonnet 5 | $0.00025 | $0.00565 |
| Haiku 4.5 | $0.00013 | $0.00283 |
Grade A, and why
faab-bidding 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 12d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Waiver Bid Sizing
Produce a specific number, not a range and a shrug. Bids are a function of four things: what class of player this is, how contested the claim will be, how much budget remains against how many chances remain, and what this league actually pays.
Step 1: Load context
Read leagues.md from the project root first — the fields that matter here are the waiver system (FAAB, continual rolling priority, weekly reverse-standings priority, or a hybrid with FCFS phases), league size, scoring (superflex especially), and playoff weeks. If the file is missing or blank, ask for them and suggest running fantasy-league-setup:league-config. If more than one league is defined, use the one marked (default).
Then ask for: remaining budget or current claim priority, the target player, and — highest leverage — recent winning bids or claim results in this league (most platforms show a transaction/bid history page). Also ask whether $0 bids are allowed, whether the platform processes claims conditionally (only one of your claims can win) or independently (every winning claim processes, so three wins can drain the budget), and whether post-waiver players become FCFS free agents immediately or after a second lock.
For any injury- or demotion-driven role change, pin the advice to an as-of timestamp and cite the evidence used. Before recommending a major bid, all-in priority burn, or a cut needed to fund the move, confirm both:
- An official status change: team transaction, practice report, inactive list, coach quote, or platform status.
- A second credible source confirming the role impact: beat reporter, national news desk, or depth-chart/practice report follow-up.
If that verification is missing or conflicting, keep the recommendation provisional: lower the aggression, avoid destructive cuts tied only to the rumor, and say to wait for waivers to process or for the next official report.
Live platform source routing. Honor a browser the user explicitly names. If leagues.md records a Preferred browser, use that when it has a signed-in session for the platform. Otherwise use any authenticated browser the current assistant already has. For Yahoo league data, prefer an authenticated browser over a connector. If a Yahoo connector returns 403, unauthorized, or an equivalent authorization failure, do not retry it during the same task. For non-Yahoo platforms, use a purpose-built connector when it is available and returns complete current data; otherwise use the browser. Read league rosters, the free-agent pool, standings, transaction history, and any rankings site directly instead of making the user paste them. Timestamp live data and name the source. The session rules from roster-ops apply unchanged: the user's session is the auth; never ask for, read, store, or type credentials; use the visible UI rather than platform endpoints; and stop and hand back on any login, 2FA, captcha, consent, or unusual-activity screen. If no usable live source exists, state the access gap and do not fabricate league-specific analysis.
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.
- 12d ago First seen · 100 lines · 127 tokens per session scan A 46cdebbe3e0a
faab-bidding is a skill published in the GitHub repository derekrbreese/fantasy-football-skills (4 stars, last pushed 28d ago), licensed MIT. It adds 127 tokens to every session and 2,827 once invoked, about $0.0006 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-31.
Other skills, from other repositories
technical-documentation
Audit, write, and improve developer documentation using Google's Developer Documentation Style Guide and Technical Writing courses. Use this skill for any documentation work, even when the user names no style guide: "audit our docs", "review this README", "write a README", "getting started guide", "how-to or…
top-design
Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "Awwwards quality", "make my site stunning", "scroll animations", "parallax storytelling", "cinematic web design", "portfolio site", or "brand experience". Also trigger when elevating a standard…
design-everyday-things
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…
design-sprint
Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate before we build", "rapid prototype", "test with users", or "should we build this". Also trigger when a team is stuck in endless debate over a high-stakes product…
improve-retention
Diagnose and fix retention problems using behavior design (B=MAP). Use when the user mentions "users sign up but dont stick around", "activation rate", "onboarding friction", "retention metrics", "why users dont complete", "churn analysis", or "aha moment". Also trigger when analyzing cohort retention curves…
steve-jobs-design-review
Review designs, products, and features with Steve Jobs' standards: ruthless simplicity, focus, and end-to-end excellence. Use when the user mentions "Steve Jobs review", "design review", "product review", "what would Steve do", "insanely great", "this feels too complicated", "too many features", "product taste"…