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 OpenLAIR/OpenSkill --skill evo-gh-data-fetchergit clone --depth 1 https://github.com/OpenLAIR/OpenSkillWrote 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/openlair/openskill/evo-gh-data-fetcher)<a href="https://agentmods.dev/skills/openlair/openskill/evo-gh-data-fetcher"><img src="https://agentmods.dev/badge/skills/openlair/openskill/evo-gh-data-fetcher/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/openlair/openskill/evo-gh-data-fetcher"><img src="https://agentmods.dev/badge/skills/openlair/openskill/evo-gh-data-fetcher.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.00062 | $0.00714 |
| Opus 5 | $0.00031 | $0.00357 |
| Sonnet 5 | $0.00012 | $0.00143 |
| Haiku 4.5 | $0.00006 | $0.00071 |
Grade A, and why
evo-gh-data-fetcher scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
description: Fetches pull request and issue data from a GitHub repository using the GitHub REST API via curl/subprocess. Handles JSON output parsing, pagination, date range filtering, and error handling. Use when you nee How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
evo-gh-data-fetcher
Fetches PR and issue data from GitHub repositories using the GitHub REST API (via curl subprocess calls). Works without gh CLI authentication by using unauthenticated API access for public repos.
Key Concepts
- Uses GitHub Search API (
/search/issues) with query qualifiers liketype:pr,type:issue,created:YYYY-MM-DD..YYYY-MM-DD - Search API returns max 1000 results per query; pagination handled automatically
- PR details (merge status, merged_at) require individual PR endpoint calls (
/repos/{owner}/{repo}/pulls/{number}) - Timestamps are ISO 8601 format with Z suffix (e.g.,
2024-12-15T10:30:00Z) - Rate limiting: unauthenticated = 60 req/hour; with token = 5000 req/hour
- PR states from API:
open,closedwithmergedboolean andmerged_attimestamp - Issue labels are returned as array of objects:
[{"name": "bug", ...}]
Usage
import sys
sys.path.insert(0, '/app/environment/skills/evo-gh-data-fetcher/scripts')
from utils import fetch_prs_fast, fetch_issues_with_labels, parse_gh_timestamp
# Fetch PRs
prs = fetch_prs_fast("cli/cli", "2024-12-01", "2024-12-31")
# Fetch Issues
issues = fetch_issues_with_labels("cli/cli", "2024-12-01", "2024-12-31")
# Parse timestamps
from datetime import datetime
dt = parse_gh_timestamp("2024-12-15T10:30:00Z")
Functions
parse_gh_timestamp(ts_string)- Parse ISO 8601 GitHub timestamp to datetimerun_github_api(url)- Execute curl to GitHub REST API, return parsed JSONfetch_search_results(query, per_page, max_pages)- Paginated search API fetcherfetch_prs_fast(repo, date_start, date_end)- Fetch PRs with merge detailsfetch_issues_with_labels(repo, date_start, date_end)- Fetch issues with labels
PR Data Structure (from /repos/{owner}/{repo}/pulls/{number})
number: intstate: "open" or "closed"merged: booleancreated_at: ISO 8601 timestampmerged_at: ISO 8601 timestamp or nullclosed_at: ISO 8601 timestamp or nulluser.login: string (author)labels: [{"name": "...", ...}]
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 65 lines · 62 tokens per session scan A 2efceb324364
evo-gh-data-fetcher is a skill published in the GitHub repository OpenLAIR/OpenSkill (88 stars, last pushed yesterday), licensed Apache-2.0. It adds 62 tokens to every session and 714 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-11.
Other skills, from other repositories
resolving-merge-conflicts
Use when a git merge or rebase reports conflicts and the operation is in progress.
yesresearch
Autonomous research loop — read plan, decompose, dispatch research agents, integrate, deliver wiki. For research tasks instead of coding. Runs as visible TUI agents in git worktree. Use when user says "yesresearch", "research ", "recherchiere ". Spawns cluster agents that use opencode built-in subagents (general…
yesloop
Autonomous task loop — analyze, plan, execute, verify, review, finish. Runs as visible TUI agent in git worktree. Use when user says "yesloop", "loop", "run it autonomously".
dos-verify-done-claims
Before accepting an agent's 'done / shipped / fixed' claim, verify it against ground truth (git ancestry + the commit's own diff) using the DOS kernel's dos verify and dos commit-audit — never the agent's own narration.
Workspace Git Hygiene
Inspect branch and status, protect user edits, and avoid destructive git commands.
Using Git Worktrees
Create or use an isolated worktree for feature work so concurrent edits do not collide.