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 besoeasy/open-skills --skill random-contributorgit clone --depth 1 https://github.com/besoeasy/open-skillsWrote 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/besoeasy/open-skills/random-contributor)<a href="https://agentmods.dev/skills/besoeasy/open-skills/random-contributor"><img src="https://agentmods.dev/badge/skills/besoeasy/open-skills/random-contributor/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/besoeasy/open-skills/random-contributor"><img src="https://agentmods.dev/badge/skills/besoeasy/open-skills/random-contributor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 43 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 70 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00029 | $0.00873 |
| Opus 5 | $0.00015 | $0.00436 |
| Sonnet 5 | $0.00006 | $0.00175 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
random-contributor 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `curl` and `jq` for Bash examples, or Node.js 18+ for JS examples. What it actually says
Random Contributor Skill
Purpose
- Select a uniformly random contributor from a public GitHub repository. Useful for sampling, shoutouts, delegation, or fair assignment among contributors.
What it does
- Uses GitHub REST API (public endpoints) to list contributors for a repo (handles pagination).
- Falls back to scraping the repository's contributors page if API rate limits or CORS prevent API use.
- Returns contributor info: login, name (if available), avatar URL, profile URL, contributions count.
When to use
- Pick a random maintainer or contributor for tasks like "who should review" or "who to credit".
- Should be used only on public repositories.
Prerequisites
curlandjqfor Bash examples, or Node.js 18+ for JS examples.- Optional GitHub token (GH_TOKEN) increases rate limits; skill works without it for small repos.
Examples
Bash (uses GitHub API; paginates with per_page=100):
REPO_OWNER=besoeasy
REPO_NAME=open-skills
# Fetch contributor list (public API). Uses optional GH_TOKEN env for higher rate limit.
AUTH_HEADER=""
if [ -n "${GH_TOKEN:-}" ]; then
AUTH_HEADER="-H \"Authorization: token ${GH_TOKEN}\""
fi
# Get contributors (first page); for large repos you'd page. Here we do simple pagination loop.
contributors=()
page=1
while true; do
out=$(eval "curl -fsS ${AUTH_HEADER} \"https://api.github.com/repos/${REPO_OWNER}/${REPO_NAME}/contributors?per_page=100&page=${page}\"")
count=$(echo "$out" | jq 'length')
if [ "$count" -eq 0 ]; then break; fi
logins=$(echo "$out" | jq -r '.[].login')
while read -r l; do contributors+=("$l"); done <<< "$logins"
if [ "$count" -lt 100 ]; then break; fi
page=$((page+1))
done
# Pick random
idx=$((RANDOM % ${#contributors[@]}))
selected=${contributors[$idx]}
echo "$selected"
Node.js (recommended: uses native fetch and handles pagination):
async function getRandomContributor(owner, repo, token) {
const headers = {};
if (token) headers['Authorization'] = `token ${token}`;
let page = 1;
const per = 100;
const all = [];
while (true) {
const url = `https://api.github.com/repos/${owner}/${repo}/contributors?per_page=${per}&page=${page}`;
const res = await fetch(url, { headers });
if (!res.ok) break;
const data = await res.json();
if (!Array.isArray(data) || data.length === 0) break;
all.push(...data);
if (data.length < per) break;
page++;
}
if (!all.length) return null;
const pick = all[Math.floor(Math.random() * all.length)];
return {
login: pick.login,
avatar: pick.avatar_url,
profile: pick.html_url,
contributions: pick.contributions
};
}
// Usage:
// getRandomContributor('besoeasy','open-skills', process.env.GH_TOKEN).then(console.log)
Agent prompt
"Find a random contributor for {owner}/{repo}. Use the GitHub API; if API rate limits block you, fall back to scraping the contributors page. Return JSON: {login, name?, avatar, profile, contributions}."
Notes & Caveats
- For very large repos (>1000 contributors) consider streaming or reservoir sampling instead of fetching all contributors at once.
- Respect GitHub API rate limits; provide an option to use GH_TOKEN to increase limits.
- Public repos only; do not attempt to access private repos without appropriate credentials.
See also
- skills/check-crypto-address-balance (example of API usage patterns)
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.
- 10d ago First seen · 107 lines · 29 tokens per session scan A c24fc868b720
random-contributor is a skill published in the GitHub repository besoeasy/open-skills (132 stars, last pushed 5d ago), licensed MIT. It adds 29 tokens to every session and 873 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill (do NOT push/PR directly) when the user says code is…
github-repo-management
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
retro
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively…
github-auth
Set up GitHub authentication for the agent using git (universally available) or the gh CLI. Covers HTTPS tokens, SSH keys, credential helpers, and gh auth — with a detection flow to pick the right method automatically.