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-report-generatorgit 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-report-generator)<a href="https://agentmods.dev/skills/openlair/openskill/evo-gh-report-generator"><img src="https://agentmods.dev/badge/skills/openlair/openskill/evo-gh-report-generator/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-report-generator"><img src="https://agentmods.dev/badge/skills/openlair/openskill/evo-gh-report-generator.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.00061 | $0.00496 |
| Opus 5 | $0.00030 | $0.00248 |
| Sonnet 5 | $0.00012 | $0.00099 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
evo-gh-report-generator 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 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.
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.
What it actually says
evo-gh-report-generator
Processes fetched PR/issue data to compute all required metrics and serialize results to report.json.
Key Concepts
- PR states: REST API returns state as 'open'/'closed' with separate 'merged' boolean
- Time-to-merge: measured from created_at to merged_at in days, rounded to 1 decimal
- Top contributor: person who opened the most PRs (by user.login)
- Bug detection: any issue where at least one label name contains substring 'bug' (case-insensitive)
- Resolved bugs: bug issues where state == 'closed'
- closed PRs: PRs with state 'closed' that are NOT merged (merged == false)
Usage
import sys
sys.path.insert(0, '/app/environment/skills/evo-gh-report-generator/scripts')
from utils import compute_pr_metrics, compute_issue_metrics, generate_report
# prs = list of PR dicts from GitHub REST API
# issues = list of issue dicts from GitHub Search API
pr_metrics = compute_pr_metrics(prs)
issue_metrics = compute_issue_metrics(issues)
report = generate_report(pr_metrics, issue_metrics, "/app/report.json")
Functions
is_bug_issue(issue_data)- Check if issue has a bug labelidentify_top_contributor(prs)- Find top PR author by countcompute_pr_metrics(prs)- Compute total/merged/closed/avg_merge_days/top_contributorcompute_issue_metrics(issues)- Compute total/bug/resolved_bugsgenerate_report(pr_metrics, issue_metrics, output_path)- Write report.json
Output Format
{
"pr": {
"total": <int>,
"merged": <int>,
"closed": <int>,
"avg_merge_days": <float>,
"top_contributor": <str>
},
"issue": {
"total": <int>,
"bug": <int>,
"resolved_bugs": <int>
}
}
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 · 60 lines · 61 tokens per session scan A 793a8c679b77
evo-gh-report-generator is a skill published in the GitHub repository OpenLAIR/OpenSkill (88 stars, last pushed yesterday), licensed Apache-2.0. It adds 61 tokens to every session and 496 once invoked, about $0.0003 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-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.