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 urmzd/dotfiles --skill community-healthgit clone --depth 1 https://github.com/urmzd/dotfilesWrote 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/urmzd/dotfiles/community-health)<a href="https://agentmods.dev/skills/urmzd/dotfiles/community-health"><img src="https://agentmods.dev/badge/skills/urmzd/dotfiles/community-health/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/urmzd/dotfiles/community-health"><img src="https://agentmods.dev/badge/skills/urmzd/dotfiles/community-health.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.00058 | $0.01169 |
| Opus 5 | $0.00029 | $0.00584 |
| Sonnet 5 | $0.00012 | $0.00234 |
| Haiku 4.5 | $0.00006 | $0.00117 |
Grade A, and why
community-health 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 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.
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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Community Health
GitHub's Community Standards checklist expects every public repo to ship a minimum set of community-health files. This skill provides the canonical templates and the placement rules. All templates live in assets/ and mirror the target repo layout.
Files and Placement
Copy each asset to the target repo path shown below. Sources are relative to this skill's assets/ directory.
| Asset source | Target path | Purpose |
|---|---|---|
CODE_OF_CONDUCT.md |
CODE_OF_CONDUCT.md |
Contributor Covenant 2.1; populates community profile. |
SECURITY.md |
SECURITY.md |
Private vulnerability reporting; populates the Security tab. |
github/pull_request_template.md |
.github/pull_request_template.md |
Single PR template used for every PR. |
github/ISSUE_TEMPLATE/bug_report.yml |
.github/ISSUE_TEMPLATE/bug_report.yml |
Structured bug report form. |
github/ISSUE_TEMPLATE/feature_request.yml |
.github/ISSUE_TEMPLATE/feature_request.yml |
Structured feature request form. |
github/ISSUE_TEMPLATE/config.yml |
.github/ISSUE_TEMPLATE/config.yml |
Disables blank issues; adds Security + Discussions contact links. |
LICENSE and CONTRIBUTING.md also show on the community profile but are owned by scaffold-project and the language-specific scaffold skills, not here.
Template Placeholders
Templates contain {PLACEHOLDER} tokens that must be replaced when copied into a target repo.
| Placeholder | Source | Example |
|---|---|---|
{OWNER} |
GitHub owner (user or org) from the remote URL or gh repo view --json owner |
urmzd |
{REPO} |
Repo name on GitHub (without owner) | sr, teasr, saige |
{CURRENT_MAJOR} |
Current major version from the project manifest (Cargo.toml, pyproject.toml, package.json, etc.). Use 0 for pre-1.0 projects and adjust the supported-versions table accordingly. |
6, 1, 0 |
{CHECK_COMMAND} |
The quality-gate command from the project's task runner | just check, npm run ci, cargo test --workspace, go test ./... |
What ships with it
6 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.
- 10d ago First seen · 78 lines · 58 tokens per session scan A 796b9d2f037c
community-health is a skill published in the GitHub repository urmzd/dotfiles (3 stars, last pushed 3d ago), licensed Apache-2.0. It adds 58 tokens to every session and 1,169 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-08-31.
Other skills, from other repositories
scan-commit
Automatically scan the repository for unstaged/untracked changes, group them into logical commits using hunk-level analysis, stage and commit them following Conventional Commits.
smart-commit
Analyze staged changes and split them into multiple logical commits following Conventional Commits.
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes.
pr-review
Intelligent PR code review with dynamic agent allocation based on change types. Analyzes PR changes and generates targeted review tasks.
analyze-pr
Analyze a GitHub/GitLab Pull Request by fetching its diff, reading its web description, and generating a comprehensive document. Use when the user provides a PR link and wants to understand what changes the PR introduces, or asks to review/analyze/summarize a pull request.
gen-commit-msg
Generate intelligent commit messages based on staged changes following Conventional Commits format.