flaim: Skill for Claude Code

.agents/skills/activity-brief/SKILL.md

activity-brief is a skill for Claude Code from jdguggs10/flaim. It costs 44 tokens per session (809 once invoked), scanned A, original, MIT.

An automated testing agent for NPM projects, which are JavaScript or TypeScript projects managed with NPM.

In plain words
What is it for?
Use it to audit coverage, create tests and test configuration, validate GitHub Actions, run tests locally, and fix detected errors.
Why use it?
It finds missing tests and testing setup, checks continuous integration workflows, and investigates test failures through repeated test-and-fix cycles.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: installed under .agents/ (shared by several agents).

This is jdguggs10/flaim's own configuration. It tells Claude Code how to work on flaim itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything flaim configures →

Part of the flaim-fantasy plugin — 3 skills, 1 MCP server shipped together

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/jdguggs10/flaim/main/.agents/skills/activity-brief/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/jdguggs10/flaim

Made for: Claude Code.

Or install flaim-fantasy, the plugin that ships this one along with the rest of its 3 skills, 1 MCP server.

Wrote 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.

agentmods badge for activity-brief

README.md
[![agentmods](https://agentmods.dev/badge/skills/jdguggs10/flaim/activity-brief.svg)](https://agentmods.dev/skills/jdguggs10/flaim/activity-brief)
Your own site
<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>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 809 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash 1c3b1895cac2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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.

.agents/skills/activity-brief/SKILL.md · 86 lines

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

  • $ARGUMENTS is 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_session result 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 defaultLeague when present, otherwise the relevant sport entry in defaultLeagues.
  • If there is no applicable default and multiple leagues still match, ask which league.
  • Call get_league_info for 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_transactions with the default count or explicit count: 25.
  • Use a larger count such as count: 40 only when the requested window is busier or longer than a normal daily brief.
  • Do not use count: 100 unless 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 week and uses a recent timestamp window.
    • ESPN and Sleeper are more week-oriented than date-oriented.

Read the full file on GitHub · 86 lines

Changes

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.

  1. 2d ago Changed 1c3b1895cac2
  2. 7d ago First seen · 86 lines · 44 tokens per session scan A eb7ba0700219

Subscribe to this mod's changes

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.

Related

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.

megamen32/gptadmin_opensource · 40 tokens

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.

cyanheads/mcp-ts-core · 46 tokens

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…

cyanheads/mcp-ts-core · 76 tokens

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.

cyanheads/mcp-ts-core · 41 tokens

systematic-debugging

4-phase root cause debugging: understand bugs before fixing.

NousResearch/hermes-agent · 16 tokens

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…

mem0ai/mem0 · 207 tokens