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 alunduil/alunduil-chezmoi --skill contributinggit clone --depth 1 https://github.com/alunduil/alunduil-chezmoiWrote 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/alunduil/alunduil-chezmoi/contributing)<a href="https://agentmods.dev/skills/alunduil/alunduil-chezmoi/contributing"><img src="https://agentmods.dev/badge/skills/alunduil/alunduil-chezmoi/contributing/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/alunduil/alunduil-chezmoi/contributing"><img src="https://agentmods.dev/badge/skills/alunduil/alunduil-chezmoi/contributing.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.00054 | $0.00440 |
| Opus 5.5 | $0.00022 | $0.00176 |
| Sonnet 5.5 | $0.00011 | $0.00088 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
contributing 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 1mo 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.
What it actually says
CONTRIBUTING
Reference: https://github.com/nayafia/contributing-template (CC0).
Is one warranted?
- Open source, accepting contributions: yes — fill in nayafia.
- Closed source / personal config / archived: no — a one-line note in the README suffices. Don't manufacture process for a project that won't use it.
- Library or tool with even occasional outside contributors: yes, even if minimal.
If not warranted, say so and stop.
Template (fill what applies, drop the rest)
- Welcome / how to contribute — issues, PRs, docs, design. Be concrete about what's wanted.
- Ground rules — code of conduct pointer, scope boundaries, what won't be accepted.
- Your first contribution — "good first issue" filter or a small task.
- Getting started — clone, prerequisites, dev loop (sensors: tests, linters, type checks). Mirror the README's install but for the contributor path.
- Reporting bugs / suggesting features — issue templates if any; otherwise required fields.
- Code review process — who reviews, turnaround, draft-PR convention if used.
- Commit / PR conventions — message style, branch naming, sign-off, PR template.
- Community — chat, mailing list — only when they exist.
Concise, friendly, action-oriented. Drop sections rather than pad.
Procedure
- Decide warranted vs. not.
- If warranted: read existing CONTRIBUTING (if any), README, and 1-2 recent PRs to learn the actual process. Don't invent process the project doesn't use.
- Surface scope and any inferences before drafting. Apply only after agreement.
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.
- 1mo ago First seen · 50 lines · 54 tokens per session scan A d3095681f6af
contributing is a skill published in the GitHub repository alunduil/alunduil-chezmoi (2 stars, last pushed today), licensed 0BSD. It adds 54 tokens to every session and 440 once invoked, about $0.0002 per session on Opus 5.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
batch-grill-me
A relentless interview that asks every frontier question at once, round by round.
dotfiles-bootstrap
Bootstrap a workstation with the dotfiles framework. Takes a GitHub user / owner+repo / explicit clone URL and runs dot config init (which shells out to chezmoi) with the right safety prompts. Honors the active agent profile (ask / plan / apply / audit) so it defaults to dry-run in safer modes and full apply in apply.
vibe
Delegate a coding task to a cheap AI model (Mistral Vibe by default, but any provider Vibe knows about — DeepSeek, Gemini Flash, etc.) and supervise the result via git diff. Claude orchestrates, the cheap model codes. Claude consumes 500-1500 tokens per delegation regardless of how many file reads the delegate does…
repository-history
Explain why code exists: Git blame, renames, reverts, and linked PRs.
draft-doc
Create and update Google Docs with gws: native Markdown with Mermaid/SVG figures, or styled .gdoc.
databricks
Operate Databricks bundles, jobs, pipelines, and Unity Catalog.