Agent skill

Openrouter Trending Models

by MadAppGang in MadAppGang/claude-code

Fetch trending programming models from OpenRouter rankings. An agent skill from MadAppGang/claude-code.

MITAuto-check passedAI & LLM Engineering

Install Openrouter Trending Models

skills CLI
$ npx skills add MadAppGang/claude-code --skill openrouter-trending-models -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install MadAppGang/claude-code openrouter-trending-models --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/MadAppGang/claude-code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/openrouter-trending-models .claude/skills/openrouter-trending-models && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
openrouter-trending-models
GitHub stars
285
Token cost
~3.6k tokens
SKILL.md length
839 words
Files
1
Skills in repo
69
Repo updated
First seen
Licence
MIT

At a glance

Fetch trending programming models from OpenRouter rankings. An agent skill from MadAppGang/claude-code.

  • Works in 5 steps: Select models for multi-model review → Research AI coding trends → Update plugin documentation → …
  • Selecting models for multi-model review
  • SKILL.md covers Overview, When to Use This Skill, Quick Start and Output Format, plus 5 more sections
  • Calls bun, jq and curl; reaches openrouter.ai

What it does

Openrouter Trending Models is an agent skill from MadAppGang/claude-code. Fetch trending programming models from OpenRouter rankings. Use when selecting models for multi-model review, updating model recommendations, or researching current AI coding trends. Provides model IDs, context windows, pricing, and usage statistics from the most recent week.

Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in AI & LLM Engineering, covering Model routing and gateways and Context engineering. It works with OpenRouter. The repository describes itself as: claude code plugins marketplace. The licence is MIT.

When your agent uses it

  • Selecting models for multi-model review
  • Updating model recommendations
  • Researching current AI coding trends

Example prompts

  • “/openrouter-trending-models”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Select models for multi-model review
  2. Research AI coding trends
  3. Update plugin documentation
  4. Cost optimization
  5. Model recommendations

What it can do on your machine

Read from SKILL.md and the folder at commit 6097ad4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • bun
    • jq
    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • openrouter.ai

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Openrouter Trending Models loads about 3.6k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 839 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~76
When it runs · the whole SKILL.md, loaded when a task matches
~3.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from MadAppGang/claude-code at commit 6097ad4, republished under its MIT licence (© MadAppGang). 839 words, ~3,571 tokens.

Download SKILL.mdSave it as .claude/skills/openrouter-trending-models/SKILL.md (or your agent's skills folder).
name
openrouter-trending-models
description
Fetch trending programming models from OpenRouter rankings. Use when selecting models for multi-model review, updating model recommendations, or researching current AI coding trends. Provides model IDs, context windows, pricing, and usage statistics from the most recent week.

Overview

This skill provides access to current trending programming models from OpenRouter's public rankings. It executes a Bun script that fetches, parses, and structures data about the top 9 most-used AI models for programming tasks.

What you get:

  • Model IDs and names (e.g., x-ai/grok-code-fast-1)
  • Token usage statistics (last week's trends)
  • Context window sizes (input capacity)
  • Pricing information (per token and per 1M tokens)
  • Summary statistics (top provider, price ranges, averages)

Data Source:

Update Frequency: Weekly (OpenRouter updates rankings every week)


When to Use This Skill

Use this skill when you need to:

  1. Select models for multi-model review

    • Plan reviewer needs current trending models
    • User asks "which models should I use for review?"
    • Updating model recommendations in agent workflows
  2. Research AI coding trends

    • Developer wants to know most popular coding models
    • Comparing model capabilities (context, pricing, usage)
    • Identifying "best value" models for specific tasks
  3. Update plugin documentation

    • Refreshing model lists in README files
    • Keeping agent prompts current with trending models
    • Documentation maintenance workflows
  4. Cost optimization

    • Finding cheapest models with sufficient context
    • Comparing pricing across trending models
    • Budget planning for AI-assisted development
  5. Model recommendations

    • User asks "what's the best model for X?"
    • Providing data-driven suggestions vs hardcoded lists
    • Offering alternatives based on requirements

Quick Start

Running the Script

Basic Usage:

bash
bun run scripts/get-trending-models.ts

Output to File:

bash
bun run scripts/get-trending-models.ts > trending-models.json

Pretty Print:

bash
bun run scripts/get-trending-models.ts | jq '.'

Help:

bash
bun run scripts/get-trending-models.ts --help
Expected Output

The script outputs structured JSON to stdout:

json
{
  "metadata": {
    "fetchedAt": "2025-11-14T10:30:00.000Z",
    "weekEnding": "2025-11-10",
    "category": "programming",
    "view": "trending"
  },
  "models": [
    {
      "rank": 1,
      "id": "x-ai/grok-code-fast-1",
      "name": "Grok Code Fast",
      "tokenUsage": 908664328688,
      "contextLength": 131072,
      "maxCompletionTokens": 32768,
      "pricing": {
        "prompt": 0.0000005,
        "completion": 0.000001,
        "promptPer1M": 0.5,
        "completionPer1M": 1.0
      }
    }
    // ... 8 more models
  ],
  "summary": {
    "totalTokens": 4500000000000,
    "topProvider": "x-ai",
    "averageContextLength": 98304,
    "priceRange": {
      "min": 0.5,
      "max": 15.0,
      "unit": "USD per 1M tokens"
    }
  }
}
Execution Time

Typical execution: 2-5 seconds

  • Fetch rankings: ~1 second
  • Fetch model details: ~1-2 seconds (parallel requests)
  • Parse and format: <1 second

Output Format

Metadata Object
typescript
{
  fetchedAt: string;        // ISO 8601 timestamp of when data was fetched
  weekEnding: string;       // YYYY-MM-DD format, end of ranking week
  category: "programming";  // Fixed category
  view: "trending";         // Fixed view type
}
Models Array (9 items)

Each model contains:

typescript
{
  rank: number;             // 1-9, position in trending list
  id: string;               // OpenRouter model ID (e.g., "x-ai/grok-code-fast-1")
  name: string;             // Human-readable name (e.g., "Grok Code Fast")
  tokenUsage: number;       // Total tokens used last week
  contextLength: number;    // Maximum input tokens
  maxCompletionTokens: number; // Maximum output tokens
  pricing: {
    prompt: number;         // Per-token input cost (USD)
    completion: number;     // Per-token output cost (USD)
    promptPer1M: number;    // Input cost per 1M tokens (USD)
    completionPer1M: number; // Output cost per 1M tokens (USD)
  }
}
Summary Object
typescript
{
  totalTokens: number;      // Sum of token usage across top 9 models
  topProvider: string;      // Most represented provider (e.g., "x-ai")
  averageContextLength: number; // Average context window size
  priceRange: {
    min: number;            // Lowest prompt price per 1M tokens
    max: number;            // Highest prompt price per 1M tokens
    unit: "USD per 1M tokens";
  }
}

Integration Examples

Example 1: Dynamic Model Selection in Agent

Scenario: Plan reviewer needs current trending models for multi-model review

markdown
# In plan-reviewer agent workflow

STEP 1: Fetch trending models
- Execute: Bash("bun run scripts/get-trending-models.ts > /tmp/trending-models.json")
- Read: /tmp/trending-models.json

STEP 2: Parse and present to user
- Extract top 3-5 models from models array
- Display with context and pricing info
- Let user select preferred model(s)

STEP 3: Use selected model for review
- Pass model ID to Claudish proxy

Implementation:

typescript
// Agent reads output
const data = JSON.parse(bashOutput);

// Extract top 5 models
const topModels = data.models.slice(0, 5);

// Present to user
const modelList = topModels.map((m, i) =>
  `${i + 1}. **${m.name}** (\`${m.id}\`)
   - Context: ${m.contextLength.toLocaleString()} tokens
   - Pricing: $${m.pricing.promptPer1M}/1M input
   - Usage: ${(m.tokenUsage / 1e9).toFixed(1)}B tokens last week`
).join('\n\n');

// Ask user to select
const userChoice = await AskUserQuestion(`Select model for review:\n\n${modelList}`);
Example 2: Find Best Value Models

Scenario: User wants high-context models at lowest cost

bash
# Fetch models and filter with jq
bun run scripts/get-trending-models.ts | jq '
  .models
  | map(select(.contextLength > 100000))
  | sort_by(.pricing.promptPer1M)
  | .[:3]
  | .[] | {
      name,
      id,
      contextLength,
      price: .pricing.promptPer1M
    }
'

Output:

json
{
  "name": "Gemini 2.5 Flash",
  "id": "google/gemini-2.5-flash",
  "contextLength": 1000000,
  "price": 0.075
}
{
  "name": "Grok Code Fast",
  "id": "x-ai/grok-code-fast-1",
  "contextLength": 131072,
  "price": 0.5
}
Example 3: Update Plugin Documentation

Scenario: Automated weekly update of README model recommendations

bash
# Fetch models
bun run scripts/get-trending-models.ts > trending.json

# Extract top 5 model names and IDs
jq -r '.models[:5] | .[] | "- `\(.id)` - \(.name) (\(.contextLength / 1024)K context, $\(.pricing.promptPer1M)/1M)"' trending.json

# Output (ready for README):
# - `x-ai/grok-code-fast-1` - Grok Code Fast (128K context, $0.5/1M)
# - `anthropic/claude-4.5-sonnet-20250929` - Claude 4.5 Sonnet (200K context, $3.0/1M)
# - `google/gemini-2.5-flash` - Gemini 2.5 Flash (976K context, $0.075/1M)

Scenario: Identify when new models enter top 9

bash
# Save current trending models
bun run scripts/get-trending-models.ts | jq '.models | map(.id)' > current.json

# Compare with previous week (saved as previous.json)
diff <(jq -r '.[]' previous.json | sort) <(jq -r '.[]' current.json | sort)

# Output shows new entries (>) and removed entries (<)

Troubleshooting

Issue: Script Fails to Fetch Rankings

Error Message:

✗ Error: Failed to fetch rankings: fetch failed

Possible Causes:

  1. No internet connection
  2. OpenRouter site is down
  3. Firewall blocking openrouter.ai
  4. URL structure changed

Solutions:

  1. Test connectivity:
bash
curl -I https://openrouter.ai/rankings
# Should return HTTP 200
  1. Check URL in browser:

  2. Check firewall/proxy:

bash
# Test from command line
curl "https://openrouter.ai/rankings?category=programming&view=trending&_rsc=2nz0s"
# Should return HTML with embedded JSON
  1. Use fallback data:
    • Keep last successful output as fallback
    • Use cached trending-models.json if < 14 days old
Issue: Parse Error (Invalid RSC Format)

Error Message:

✗ Error: Failed to extract JSON from RSC format

Cause: OpenRouter changed their page structure

Solutions:

  1. Inspect raw HTML:
bash
curl "https://openrouter.ai/rankings?category=programming&view=trending&_rsc=2nz0s" | head -200
  1. Look for data pattern:

    • Search for "data":[{ in output
    • Check if line starts with different prefix (not 1b:)
    • Verify JSON structure matches expected format
  2. Update regex in script:

    • Edit scripts/get-trending-models.ts
    • Modify regex in fetchRankings() function
    • Test with new pattern
  3. Report issue:

    • File issue in plugin repository
    • Include raw HTML sample (first 500 chars)
    • Specify when error started occurring
Show full SKILL.md (348 more words)Show less
Issue: Model Details Not Found

Warning Message:

Warning: Model x-ai/grok-code-fast-1 not found in API, using defaults

Cause: Model ID in rankings doesn't match API

Impact: Model will have 0 values for context/pricing

Solutions:

  1. Verify model exists in API:
bash
curl "https://openrouter.ai/api/v1/models" | jq '.data[] | select(.id == "x-ai/grok-code-fast-1")'
  1. Check for ID mismatches:

    • Rankings may use different ID format
    • API might have model under different name
    • Model may be new and not yet in API
  2. Manual correction:

    • Edit output JSON file
    • Add correct details from OpenRouter website
    • Note discrepancy for future fixes
Issue: Stale Data Warning

Symptom: Models seem outdated compared to OpenRouter site

Check data age:

bash
jq '.metadata.fetchedAt' trending-models.json
# Compare with current date

Solutions:

  1. Re-run script:
bash
bun run scripts/get-trending-models.ts > trending-models.json
  1. Set up weekly refresh:

    • Add to cron: 0 0 * * 1 cd /path/to/repo && bun run scripts/get-trending-models.ts > skills/openrouter-trending-models/trending-models.json
    • Or use GitHub Actions (see Automation section)
  2. Add staleness check in agents:

typescript
const data = JSON.parse(readFile("trending-models.json"));
const fetchedDate = new Date(data.metadata.fetchedAt);
const daysSinceUpdate = (Date.now() - fetchedDate.getTime()) / (1000 * 60 * 60 * 24);

if (daysSinceUpdate > 7) {
  console.warn("Data is over 7 days old, consider refreshing");
}

Best Practices

Data Freshness

Recommended Update Schedule:

  • Weekly: Ideal (matches OpenRouter update cycle)
  • Bi-weekly: Acceptable for stable periods
  • Monthly: Minimum for production use

Staleness Guidelines:

  • 0-7 days: Fresh (green)
  • 8-14 days: Slightly stale (yellow)
  • 15-30 days: Stale (orange)
  • 30+ days: Very stale (red)
Caching Strategy

When to cache:

  • Multiple agents need same data
  • Frequent model selection workflows
  • Avoiding rate limits

How to cache:

  1. Run script once: bun run scripts/get-trending-models.ts > trending-models.json
  2. Commit to repository (under skills/openrouter-trending-models/)
  3. Agents read from file instead of re-running script
  4. Refresh weekly via manual run or automation

Cache invalidation:

bash
# Check if cache is stale (> 7 days)
if [ $(find trending-models.json -mtime +7) ]; then
  echo "Cache is stale, refreshing..."
  bun run scripts/get-trending-models.ts > trending-models.json
fi
Error Handling in Agents

Graceful degradation pattern:

markdown
1. Try to fetch fresh data
   - Run: bun run scripts/get-trending-models.ts
   - If succeeds: Use fresh data
   - If fails: Continue to step 2

2. Try cached data
   - Check if trending-models.json exists
   - Check if < 14 days old
   - If valid: Use cached data
   - If not: Continue to step 3

3. Fallback to hardcoded models
   - Use known good models from agent prompt
   - Warn user data may be outdated
   - Suggest manual refresh
Integration Patterns

Pattern 1: On-Demand (Fresh Data)

bash
# Run before each use
bun run scripts/get-trending-models.ts > /tmp/models.json
# Read from /tmp/models.json

Pattern 2: Cached (Fast Access)

bash
# Check cache age first
CACHE_FILE="skills/openrouter-trending-models/trending-models.json"
if [ ! -f "$CACHE_FILE" ] || [ $(find "$CACHE_FILE" -mtime +7) ]; then
  bun run scripts/get-trending-models.ts > "$CACHE_FILE"
fi
# Read from cache

Pattern 3: Background Refresh (Non-Blocking)

bash
# Start refresh in background (don't wait)
bun run scripts/get-trending-models.ts > trending-models.json &

# Continue with workflow
# Use cached data if available
# Fresh data will be ready for next run

Changelog

v1.0.0 (2025-11-14)
  • Initial release
  • Fetch top 9 trending programming models from OpenRouter
  • Parse RSC streaming format
  • Include context length, pricing, and token usage
  • Zero dependencies (Bun built-in APIs only)
  • Comprehensive error handling
  • Summary statistics (total tokens, top provider, price range)

Future Enhancements

Planned Features
  • Category selection (programming, creative, analysis, etc.)
  • Historical trend tracking (compare week-over-week)
  • Provider filtering (focus on specific providers)
  • Cost calculator (estimate workflow costs)
Research Ideas
  • Correlate rankings with model performance benchmarks
  • Identify "best value" models (performance/price ratio)
  • Predict upcoming trending models
  • Multi-category analysis

Skill Version: 1.0.0 Last Updated: November 14, 2025 Maintenance: Weekly refresh recommended Dependencies: Bun runtime, internet connection

© MadAppGang, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/openrouter-trending-models of MadAppGang/claude-code.

Open the folder on GitHubat commit 6097ad4

Compare with similar skills

Openrouter Trending Models next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Openrouter Trending Models compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Openrouter Trending Models this skillMadAppGang/claude-code285—~3.6kAutomated safety check: PassMIT
Openrouter Context Optimizationjeremylongshore/tons-of-skills-marketplace2.8k—~2.4kAutomated safety check: PassMIT
Claudish UsageMadAppGang/claudish1k—~9kAutomated safety check: PassNone
Run Deep Swesickn33/agentic-awesome-skills47k1 repos~1.2kAutomated safety check: PassMIT
QuorumDetrol/quorum-cli119—~807Automated safety check: NotesCustom licence
OpenCode Agent Provider for NanoClawnanocoai/nanoclaw31k—~5kAutomated safety check: NotesMIT

Similar skills

  • Openrouter Context Optimization

    jeremylongshore/tons-of-skills-marketplace

    Optimize context window usage for OpenRouter models to reduce cost and improve quality.

    2.8k GitHub stars~2.4k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed
  • Claudish Usage

    MadAppGang/claudish

    CRITICAL - Guide for using Claudish CLI ONLY through sub-agents to run Claude Code with any AI model (OpenRouter, Gemini, OpenAI, local models).

    1k GitHub stars~9k tokensUpdated 4 days ago
    Agent WorkflowsAuto-check passed
  • Run Deep Swe

    sickn33/agentic-awesome-skills

    Run reproducible DeepSWE coding-agent benchmark evaluations through OpenRouter and mini-swe-agent.

    47k GitHub starsUsed in 1 repo~1.2k tokens
    AI & LLM EngineeringAuto-check passed
  • Quorum

    Detrol/quorum-cli

    Run a structured debate between agent CLIs (claude, codex, agy, grok) and the user's configured API or local models (OpenAI, Anthropic, Google, xAI, OpenRouter, Ollama and more) through the Quorum…

    119 GitHub stars~807 tokensUpdated 14 days ago
    AI & LLM EngineeringAuto-check: notes
  • Installs OpenCode as an optional NanoClaw agent runtime, reaching OpenRouter, OpenAI, Google, DeepSeek and others through OpenCode's own configuration.

    31k GitHub stars~5k tokensUpdated today
    AI & LLM EngineeringAuto-check: notes
  • Darwinian Evolver

    Luciole-Studio/Misaka-Agent

    Evolve prompts/regex/SQL/code with Imbue's evolution loop. An agent skill from Luciole-Studio/Misaka-Agent.

    171 GitHub starsUsed in 2 repos~2.1k tokens
    AI & LLM EngineeringAuto-check: warnings

More from MadAppGang/claude-code

All 69 skills in this repo
  • Content Brief

    MadAppGang/claude-code

    Content brief template and creation methodology for SEO-optimized content.

    285 GitHub starsUsed in 1 repo~959 tokens
    Auto-check passed
  • Context Detection

    MadAppGang/claude-code

    A skill your agent uses when detecting project technology stack from files/configs/directory structure, auto-loading framework-specific skills, or analyzing multi-stack fullstack projects (e.g…

    285 GitHub stars~5.4k tokensUpdated 7 mo ago
    Auto-check passed
  • Content Optimizer

    MadAppGang/claude-code

    On-page SEO optimization techniques including keyword density, meta tags, heading structure, and readability.

    285 GitHub starsUsed in 1 repo~694 tokens
    Auto-check passed
  • Keyword Cluster Builder

    MadAppGang/claude-code

    Techniques for expanding seed keywords and clustering by topic and intent.

    285 GitHub starsUsed in 1 repo~674 tokens
    Auto-check passed
  • Serp Analysis

    MadAppGang/claude-code

    SERP analysis techniques for intent classification, feature identification, and competitive intelligence.

    285 GitHub starsUsed in 1 repo~1k tokens
    Auto-check passed
  • Agent Coordination Discipline

    MadAppGang/claude-code

    A skill your agent uses when deciding whether to launch an agent, selecting which agent to use, or coordinating multiple agents.

    285 GitHub stars~3.8k tokensUpdated 7 mo ago
    Auto-check passed

Works with

Questions about Openrouter Trending Models

What does Openrouter Trending Models do?

Fetch trending programming models from OpenRouter rankings. An agent skill from MadAppGang/claude-code. Openrouter Trending Models is an agent skill from MadAppGang/claude-code. Fetch trending programming models from OpenRouter rankings.

When should I use Openrouter Trending Models?

Openrouter Trending Models fits situations like: selecting models for multi-model review; updating model recommendations; researching current AI coding trends.

How do I install Openrouter Trending Models in Claude Code?

Run `npx skills add MadAppGang/claude-code --skill openrouter-trending-models -a claude-code`. Or copy the skill folder (skills/openrouter-trending-models in MadAppGang/claude-code) into .claude/skills/openrouter-trending-models in your project. Claude Code loads it when a task matches its description.

How do I install Openrouter Trending Models in Codex?

Run `npx skills add MadAppGang/claude-code --skill openrouter-trending-models -a codex`. Or copy the skill folder (skills/openrouter-trending-models in MadAppGang/claude-code) into .agents/skills/openrouter-trending-models in your project. Codex loads it when a task matches its description.

Can I use Openrouter Trending Models in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MadAppGang/claude-code --skill openrouter-trending-models -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/openrouter-trending-models, .gemini/skills/openrouter-trending-models, .github/skills/openrouter-trending-models and .opencode/skills/openrouter-trending-models in your project.

What does Openrouter Trending Models need to run?

Going by SKILL.md and its folder, Openrouter Trending Models needs the command-line tools its instructions call (bun, jq and curl).

Does Openrouter Trending Models access the network?

SKILL.md names 1 domain. In commands or code: openrouter.ai; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Openrouter Trending Models safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Openrouter Trending Models use?

Openrouter Trending Models is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Openrouter Trending Models use?

About 3.6k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Openrouter Trending Models?

Skills that share tags, products or a category with Openrouter Trending Models: Openrouter Context Optimization (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Claudish Usage (MadAppGang/claudish, 1k stars), Run Deep Swe (sickn33/agentic-awesome-skills, 47k stars) and Quorum (Detrol/quorum-cli, 119 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Openrouter Trending Models?

MadAppGang (a GitHub organization) maintains it in MadAppGang/claude-code, which has 285 GitHub stars. The repository holds 69 skills in this directory. The repository was last updated on March 15, 2026.

Source: MadAppGang/claude-code on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.