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 chiruu12/OSS-Skills --skill oss-find-issuegit clone --depth 1 https://github.com/chiruu12/OSS-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/chiruu12/oss-skills/oss-find-issue)<a href="https://agentmods.dev/skills/chiruu12/oss-skills/oss-find-issue"><img src="https://agentmods.dev/badge/skills/chiruu12/oss-skills/oss-find-issue/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/chiruu12/oss-skills/oss-find-issue"><img src="https://agentmods.dev/badge/skills/chiruu12/oss-skills/oss-find-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Excessive Agency · line 333 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00087 | $0.04173 |
| Opus 5 | $0.00044 | $0.02086 |
| Sonnet 5 | $0.00017 | $0.00835 |
| Haiku 4.5 | $0.00009 | $0.00417 |
Grade A, and why
oss-find-issue 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find Issue
Find a real, unclaimed issue that matches your skills. from repos that actually want your contribution. This skill does the research; you decide what's worth your time.
Purpose
Not every issue is worth picking up. Random issues filed by drive-by users often get closed without merging. Issues from maintainers and org members are the ones that get reviewed and merged. This skill finds those, checks if the repo accepts outside contributions, and matches issues to what you actually know. so you don't waste weeks on something that gets rejected or ignored.
Prerequisites
- A GitHub account with
ghCLI authenticated - A target repo or area of interest (language, framework, domain)
Process
1. Understand the contributor
Before searching for anything, understand who's contributing. Ask the user:
- "What languages and frameworks are you comfortable with?"
- "What's your experience level? (first contribution / a few PRs merged / experienced contributor)"
- "Any specific repos or domains you're interested in? (web, CLI tools, data, infra, etc.)"
Do NOT skip this. Issue matching without knowing the contributor is useless.
2. Check contribution eligibility
Before looking at a single issue, verify the repo accepts outside contributions:
# Fetch contribution guidelines
gh api repos/{owner}/{repo}/contents/CONTRIBUTING.md --jq '.content' | base64 -d 2>/dev/null
gh api repos/{owner}/{repo}/contents/.github/CONTRIBUTING.md --jq '.content' | base64 -d 2>/dev/null
gh api repos/{owner}/{repo}/contents/CODE_OF_CONDUCT.md --jq '.content' | base64 -d 2>/dev/null
Check for:
- Explicit "we welcome contributions": if absent, that's a yellow flag
- CLA requirements: some orgs require signing a Contributor License Agreement before any PR
- "Internal only" signals: some repos state contributions are restricted to org members
- Stale contribution docs: if CONTRIBUTING.md references tools/processes from 3+ years ago, the repo may not be actively maintained
- Recent external PRs merged: strongest signal that outside contributions are welcome
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.
- 12d ago First seen · 336 lines · 87 tokens per session scan A 4358394d0507
oss-find-issue is a skill published in the GitHub repository chiruu12/OSS-Skills (63 stars, last pushed 19d ago), licensed MIT. It adds 87 tokens to every session and 4,173 once invoked, about $0.0004 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.
Other skills, from other repositories
conventional-commit
Workflow for generating conventional commit messages following the Conventional Commits specification. MUST be invoked every time a commit is created. Guides construction of standardized commit messages with correct type, scope, description, body, and footer.
update-changelog
Update the CHANGELOG.md files of C# projects. Parameters: csroot C# SDK repository root.
writing-clearly-and-concisely
Apply whenever writing content a human will read — emails, documents, reports, documentation, messages, UI copy, commit messages, explanations, or any other prose. Applies Strunk's timeless rules for clearer, stronger, more professional writing.
commit
Stage, commit, push, open a PR, and merge to main. Use ONLY on explicit commit intent — user says "commit", "ship it", "push this", "open a PR", "merge to main", "let's commit this", or prefixes with /commit. Do NOT auto-invoke on vague end-of-task phrases ("we're done", "wrap up") — those require explicit…
git-commit
Generate conventional commit messages for Java projects. Use when user says "commit", "create commit", "commit changes", or after completing code changes that need to be committed.
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.