Borrowing it
Nothing to install: this file belongs to jdguggs10/flaim. 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/jdguggs10/flaim/main/.agents/skills/activity-brief/SKILL.mdgit clone --depth 1 https://github.com/jdguggs10/flaimWrote 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/jdguggs10/flaim/activity-brief)<a href="https://agentmods.dev/skills/jdguggs10/flaim/activity-brief"><img src="https://agentmods.dev/badge/skills/jdguggs10/flaim/activity-brief.svg" alt="Measured on agentmods" 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.00044 | $0.00809 |
| Opus 5 | $0.00022 | $0.00404 |
| Sonnet 5 | $0.00009 | $0.00162 |
| Haiku 4.5 | $0.00004 | $0.00081 |
Grade A, and why
activity-brief 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Activity Brief
Produce a clean recent-activity briefing for the user's current or specified fantasy league.
Scope and data rules
- Fantasy league data must come from Flaim MCP tools.
- Use web search to enrich player news, injuries, role changes, and schedule context.
Arguments
$ARGUMENTSis the requested number of days back.- If no argument is provided, default to
2. - Treat non-numeric arguments as no argument unless the user clearly explains a different time window in natural language.
Workflow
1. Resolve the target league
- Reuse a usable successful
get_user_sessionresult from this chat. Call it if that context is missing, after a successful league refresh, or when the user confirms account, connection, league-list, or default changes. Do not repeat it just for a follow-up or a switch to another league already in the session result. Follow the tool's error guidance if a lookup fails. - If the user explicitly names a league, platform, or sport, honor that.
- Otherwise treat this as a vague singular request: use
defaultLeaguewhen present, otherwise the relevant sport entry indefaultLeagues. - If there is no applicable default and multiple leagues still match, ask which league.
- Call
get_league_infofor the selected league before interpreting transactions so team names and owner/team mapping are resolved.
2. Pull recent transactions
- For daily or 24-hour briefs, call
get_transactionswith the default count or explicitcount: 25. - Use a larger count such as
count: 40only when the requested window is busier or longer than a normal daily brief. - Do not use
count: 100unless the user asks for an exhaustive or full-week activity audit. - Retrieve the recent transaction window the platform provides, then trim the presentation to the requested day range.
- Remember platform caveats:
- Yahoo ignores explicit
weekand uses a recent timestamp window. - ESPN and Sleeper are more week-oriented than date-oriented.
- Yahoo ignores explicit
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 1c3b1895cac2
- 7d ago First seen · 86 lines · 44 tokens per session scan A eb7ba0700219
activity-brief is a skill published in the GitHub repository jdguggs10/flaim (17 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 809 once invoked, about $0.0002 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
gptadmin-mcp-testing
Verify a Memos-style MCP integration through GPTADMIN without duplicating the backend, leaking credentials, or confusing the native ShellMCP supervisor with legacy per-agent services.
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
field-test
Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, and produces a tight report with concrete findings and numbered follow-up options. Use after adding or modifying definitions, or when the user asks to…
add-test
Scaffold a test file for an existing tool, resource, or service. Use when the user asks to add tests, improve coverage, or when a definition exists without a matching test file.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…