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 AmineDjeghri/personal-os-setup --skill github-community-health-filesgit clone --depth 1 https://github.com/AmineDjeghri/personal-os-setupWrote 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/aminedjeghri/personal-os-setup/github-community-health-files)<a href="https://agentmods.dev/skills/aminedjeghri/personal-os-setup/github-community-health-files"><img src="https://agentmods.dev/badge/skills/aminedjeghri/personal-os-setup/github-community-health-files/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/aminedjeghri/personal-os-setup/github-community-health-files"><img src="https://agentmods.dev/badge/skills/aminedjeghri/personal-os-setup/github-community-health-files.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.00035 | $0.01831 |
| Opus 5.5 | $0.00014 | $0.00732 |
| Sonnet 5.5 | $0.00007 | $0.00366 |
| Haiku 4.5 | $0.00003 | $0.00183 |
Grade B, and why
github-community-health-files scanned grade B 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 18d 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
`git clean -fd`, and `rm -rf` are gated behind a consent prompt and time out with no Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Community Health Files
Detect which GitHub standard/community files a repo is missing, then generate them with ready-to-use templates and open a PR. Applies to any public (or private) repo that should pass GitHub's community-profile health check.
Trigger conditions
- User asks about "missing files", "SECURITY.md", "LICENSE", "CONTRIBUTING", "CODE_OF_CONDUCT", or "standard GitHub files" for a repo.
- User wants the repo to look professional / pass GitHub's community-profile check.
1. Detect missing files (authoritative)
Use GitHub's own community-profile API — do NOT guess:
# Missing files (value == null)
gh api repos/$OWNER/$REPO/community/profile \
--jq '.files | to_entries | map(select(.value == null)) | map(.key)'
# Present files
gh api repos/$OWNER/$REPO/community/profile \
--jq '.files | to_entries | map(select(.value != null)) | .[].key'
The .files keys are: code_of_conduct, code_of_conduct_file, contributing,
issue_template, license, pull_request_template, readme.
Always also list the repo root to confirm (some files like SECURITY.md and
.github/FUNDING.yml are not all in the community-profile .files set):
gh api repos/$OWNER/$REPO/contents --jq '.[] | .name'
gh api repos/$OWNER/$REPO/contents/.github --jq '.[] | .name'
2. Files to add for a public repo
| File | Content |
|---|---|
SECURITY.md |
Private vuln reporting (GitHub security advisories; add a dedicated public email only if the user supplies one), supported versions, no-public-disclosure policy, 48h response SLA. |
LICENSE |
MIT is the common OSS default; Apache-2.0 if preferred. |
CONTRIBUTING.md |
Dev setup, bug/feature reporting, branch/PR workflow, commit conventions, release process. |
CODE_OF_CONDUCT.md |
Contributor Covenant v2.1 (GitHub standard). |
.github/FUNDING.yml |
GitHub Sponsors / Ko-fi placeholder comments for user to fill. |
Tailor the repo-specific bits (maintainer email, repo URL, commit conventions, release tooling) to the actual project — read README / repository.yaml / CI first.
What ships with it
1 file 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.
- 18d ago Changed · +1 lines 4ca3000aedf0
- 27d ago First seen · 134 lines · 35 tokens per session scan B 9be9a51a88b4
github-community-health-files is a skill published in the GitHub repository AmineDjeghri/personal-os-setup (654 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 1,831 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-19.
Other skills, from other repositories
hula-skill
HuLa project skill for frontend (Vue 3 + Vite + UnoCSS + Naive UI/Vant), backend (Tauri v2 + Rust + SeaORM/SQLite), full-stack flows, and build/release work. Use when the user mentions hula or HuLa or requests changes in this repository; after triggering, ask which scope (frontend/backend/fullstack/build-release) to…
open-sourcing
This skill should be used when the user asks to "open source this project", "prepare this repository for public release", "make this repo public", "check open-source readiness", "choose a license for this project", or "set up release automation" ahead of a public launch. Provides a release-readiness workflow covering…
repo-prep
Interactively prepare a code repository for publication — LICENSE, NOTICE, AUTHORSHIP, README sections, package metadata, .gitignore, community docs (CONTRIBUTING/CODEOFCONDUCT/SECURITY/CHANGELOG), .github templates (issues/PR/CI/dependabot), a promo "more from the author" block, and conditional EU/Germany legal…
compliance-license-audit
Interactive open-source license compliance audit to identify all dependency licenses, flag risks, and detect license incompatibilities.
open-source
Open source readiness best practices. Covers licensing, documentation, community health, CI/CD, compliance, legal, and packaging. USE WHEN: user mentions "open source", "license", "LICENSE", "CONTRIBUTING", "CODEOFCONDUCT", "CHANGELOG", "open source readiness", "community health", "OSS compliance", "SPDX", "CLA"…
compliance-notice-generate
Generate NOTICE, ATTRIBUTION, or THIRD-PARTY-NOTICES files from detected dependency licenses to fulfill open-source license obligations.